From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24528] stapbpf-next housekeeping: bpf-translate.cxx should distinguish codegen for kernel/userspace targets
Date: Fri, 21 Jun 2019 15:12:00 -0000 [thread overview]
Message-ID: <bug-24528-6586-v3poQU6CUh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24528-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24528
--- Comment #2 from Serhei Makarov <me at serhei dot io> ---
Added some basic checking and error messages. Keeping PR open since we also
want to do a pass over tapset functions in case some are userspace-only. We
could mark this with a /* bpf_userspace */ annotation (bikeshed colour choice
pending).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-06-21 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 16:25 [Bug bpf/24528] New: bpf-next " me at serhei dot io
2019-05-06 17:04 ` [Bug bpf/24528] " me at serhei dot io
2019-05-06 17:07 ` [Bug bpf/24528] stapbpf-next " me at serhei dot io
2019-06-20 17:30 ` me at serhei dot io
2019-06-21 15:12 ` me at serhei dot io [this message]
2019-06-26 20:29 ` me at serhei dot io
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=bug-24528-6586-v3poQU6CUh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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.
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).