From: John Soo <jsoo1@asu.edu>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 42227@debbugs.gnu.org
Subject: [bug#42227] BPF in linux-libre
Date: Thu, 30 Jul 2020 19:20:27 -0700 [thread overview]
Message-ID: <87v9i48lxw.fsf@asu.edu> (raw)
In-Reply-To: <87d04cvnxk.fsf@gnu.org> (Mathieu Othacehe's message of "Thu, 30 Jul 2020 20:48:55 +0200")
Hi Mathieu!
> Thanks for your patience!
No problem. I'm quite busy too.
>> I also added debugfs as a requirement for a bpf system. To use it
>> %bpf-file-systems can be used in place of %base-file-systems in the
>> operating system definition.
>
> Actually, I wonder if we could mount debugfs by default, by adding it to
> %base-file-systems. Any objections?
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.
> In the meantime I pushed the bcc patch with a few edits. Regarding
> bpftrace, I'd like to avoid the "-DHAVE_BFD_DISASM=OFF" patching, I
> found this ticket which seems related:
> https://github.com/iovisor/bpftrace/issues/1106, but didn't make any
> significant progress yet.
I have tried every which way I can to make HAVE_BFD_DISASM work. A kind
persn from the bpftrace irc directed me to this PR:
https://github.com/iovisor/bpftrace/pull/1095
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.
Thanks again!
- John
next prev parent reply other threads:[~2020-07-31 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44046537-51AD-4BD7-8442-41738C4D8C98@asu.edu>
[not found] ` <87lfkqknla.fsf@gnu.org>
[not found] ` <87h7vdd6ms.fsf@asu.edu>
[not found] ` <87wo46uhdr.fsf@gnu.org>
[not found] ` <87zh8wph7h.fsf@asu.edu>
[not found] ` <87wo3uxfrq.fsf@gnu.org>
[not found] ` <871rlsegf2.fsf@asu.edu>
[not found] ` <87h7umjruz.fsf@gnu.org>
[not found] ` <87zh8dlbeu.fsf@asu.edu>
2020-07-06 13:26 ` [bug#42227] BPF in linux-libre Mathieu Othacehe
2020-07-11 16:28 ` John Soo
2020-07-30 18:48 ` Mathieu Othacehe
2020-07-31 2:20 ` John Soo [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9i48lxw.fsf@asu.edu \
--to=jsoo1@asu.edu \
--cc=42227@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).