From: Yonghong Song <yonghong.song@linux.dev>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Compiled BPF and toolchains
Date: Wed, 21 Feb 2024 08:32:05 -0800 [thread overview]
Message-ID: <96df18fa-6ce6-412e-bab9-5ca8fb7b0e6f@linux.dev> (raw)
In-Reply-To: <87frxm2hwx.fsf@oracle.com>
On 2/21/24 3:09 AM, Jose E. Marchesi wrote:
> The discussions we had last year in LSFMMBPF about BPF support in GCC
> were very useful, and led to more and better interactions between the
> BPF GCC maintainers, the BPF clang maintainers and the rest of the BPF
> community. This helped a lot to achieve better convergence with clang.
>
> We think it would be good to repeat the experience this year with a
> session where we could discuss particular topics related to compiled BPF
> in general, like the toolchain requirements introduced by the new
> features being proposed for BPF (such as supporting segmented stacks,
It will be shadow stack, as suggested by Alexei, in order to
maintain the current seemless support for stack backtracing.
> just to mention a recent one) and how to better support these in both
> GCC and clang.
Another topic worth gcc involvement is potential compiler support for
static key in bpf programs.
https://lore.kernel.org/bpf/CAADnVQJ+_+ok_io1_W7e5z_dZhxSqhEFZQkumRgmY4AJRYwW7g@mail.gmail.com/
prev parent reply other threads:[~2024-02-21 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 11:09 [LSF/MM/BPF TOPIC] Compiled BPF and toolchains Jose E. Marchesi
2024-02-21 16:32 ` Yonghong Song [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=96df18fa-6ce6-412e-bab9-5ca8fb7b0e6f@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=jose.marchesi@oracle.com \
--cc=lsf-pc@lists.linux-foundation.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