From: Mathieu Othacehe <othacehe@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: 42227-done@debbugs.gnu.org
Subject: bug#42227: BPF in linux-libre
Date: Fri, 31 Jul 2020 13:04:47 +0200 [thread overview]
Message-ID: <87r1ss0wts.fsf@gnu.org> (raw)
In-Reply-To: <87v9i48lxw.fsf@asu.edu> (John Soo's message of "Thu, 30 Jul 2020 19:20:27 -0700")
Hey,
> That seems ok. I did find a few questions about debugfs on old irc logs
> and mailing lists. My only concern again is that I would prefer to opt
> in to such a thing. debugfs is much simpler than the bpf kernel flags
> though, so maybe it will be ok to remove in the future.
Yeah, but I saw that Ubuntu for instance is enabling it by default, so I
guess it could help to have the same behaviour in Guix System. Added it
with: 6bb07e91e1ab9367f636a3a5e9d52a9e0772aa89.
> But I cannot see anything guix does differently that would cause it to
> fail. My only feeling is perhaps our configure flags for binutils might
> be causing the issue.
>
> As is, however, bpftrace does work even with out HAVE_BFD_DISASM and I
> even used it to debug a few processes recently.
Gave it another try and I think if we could get "binutils" to produce a
dynamic version of libbfd.a, that would make the trick. Anyway, let's
proceed without BFD support for now. Pushed bpftrace as
c55acb073248392b1387017378f36a1d378fa7c4.
Closing the serie, thank you!
Mathieu
prev parent reply other threads:[~2020-07-31 11:06 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 ` [bug#42227] " Mathieu Othacehe
2020-07-11 16:28 ` John Soo
2020-07-30 18:48 ` Mathieu Othacehe
2020-07-31 2:20 ` John Soo
2020-07-31 11:04 ` Mathieu Othacehe [this message]
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=87r1ss0wts.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=42227-done@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.