From: Mathieu Othacehe <othacehe@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: 42227@debbugs.gnu.org
Subject: [bug#42227] BPF in linux-libre
Date: Mon, 06 Jul 2020 15:26:11 +0200 [thread overview]
Message-ID: <87d0587p1o.fsf@gnu.org> (raw)
In-Reply-To: <87zh8dlbeu.fsf@asu.edu> (John Soo's message of "Sun, 05 Jul 2020 17:44:41 -0700")
Hey John,
> I think I tidied up the description to match the Guix situation. What do
> you think now?
Yes it's fine, thanks for the updated serie! I pushed the first patch
and patches two and three squashed together.
> I could see it being a useful default. BPF seems like a nice technology
> but I am making these patches to experiment with it myself. Because I
> haven't used it much I can't really speak on the pros of making it
> default. Other than my gut feeling that seems like something that
> should be opted into rather than opting out of I have no strong feelings
> on including it by default. The only other downside I see is that
> putting in the default might make the linux definitions less composable.
> The way it is now, one can assemble a (mostly) bpf-capable system from
> the pieces in gnu/packages/linux.scm.
Ok, thanks for explaining. I don't have much experience with BPF
either. For now we can work with a separate linux-libre, and will see
about merging it into the default, when we'll have more perspective.
I'll take more time to review patches 4 and 5. However, while trying
some of the examples packaged by BCC, I have the following error:
--8<---------------cut here---------------start------------->8---
mathieu@meru:~/guix-master$ /gnu/store/rv51f9n1w9i92m9qsg9k3ilsy3hyhjf3-bcc-0.15.0/share/bcc/tools/execsnoop
Traceback (most recent call last):
File "/gnu/store/rv51f9n1w9i92m9qsg9k3ilsy3hyhjf3-bcc-0.15.0/share/bcc/tools/execsnoop", line 21, in <module>
from bcc import BPF
ModuleNotFoundError: No module named 'bcc'
--8<---------------cut here---------------end--------------->8---
I think an additional wrapping is necessary. Could you please have a
look? I'm also removing help-guix, and opening a proper guix-patches
ticket.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-07-06 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 3:21 BPF in linux-libre John Soo
2020-06-14 9:23 ` Mathieu Othacehe
2020-06-14 15:11 ` John Soo
2020-06-17 10:16 ` Mathieu Othacehe
2020-06-17 13:42 ` John Soo
2020-06-21 15:32 ` John Soo
2020-06-26 10:50 ` Mathieu Othacehe
2020-06-28 20:24 ` John Soo
2020-07-01 5:40 ` John Soo
2020-07-03 16:01 ` John Soo
2020-07-05 8:18 ` Mathieu Othacehe
2020-07-05 8:20 ` Mathieu Othacehe
2020-07-06 0:44 ` John Soo
2020-07-06 13:26 ` Mathieu Othacehe [this message]
2020-07-11 16:28 ` [bug#42227] " John Soo
2020-07-30 18:48 ` Mathieu Othacehe
2020-07-31 2:20 ` John Soo
2020-07-31 11:04 ` bug#42227: " Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0587p1o.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=42227@debbugs.gnu.org \
--cc=jsoo1@asu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.