From: Eduard Zingerman <eddyz87@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>,
bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
kernel-team@fb.com, jose.marchesi@oracle.com
Subject: Re: [PATCH bpf-next v2 1/5] bpf: rename nocsr -> bpf_fastcall in verifier
Date: Wed, 21 Aug 2024 18:43:01 -0700 [thread overview]
Message-ID: <b0cef1d8665baac74a173dbae37db884989b170b.camel@gmail.com> (raw)
In-Reply-To: <19598881-6347-4f8b-b9f9-825366e0e536@linux.dev>
On Wed, 2024-08-21 at 18:17 -0700, Yonghong Song wrote:
> On 8/16/24 6:51 PM, Eduard Zingerman wrote:
> > Attribute used by LLVM implementation of the feature had been changed
> > from no_caller_saved_registers to bpf_fastcall (see [1]).
> > This commit replaces references to nocsr by references to bpf_fastcall
> > to keep LLVM and Kernel parts in sync.
> >
> > [1] https://github.com/llvm/llvm-project/pull/101228
>
> Let us change this link to
>
> https://github.com/llvm/llvm-project/pull/105417
Sure, will do, thank you for the review.
[...]
next prev parent reply other threads:[~2024-08-22 1:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 1:51 [PATCH bpf-next v2 0/5] support bpf_fastcall patterns for calls to kfuncs Eduard Zingerman
2024-08-17 1:51 ` [PATCH bpf-next v2 1/5] bpf: rename nocsr -> bpf_fastcall in verifier Eduard Zingerman
2024-08-22 1:14 ` Yonghong Song
2024-08-22 1:17 ` Yonghong Song
2024-08-22 1:43 ` Eduard Zingerman [this message]
2024-08-17 1:51 ` [PATCH bpf-next v2 2/5] selftests/bpf: rename nocsr -> bpf_fastcall in selftests Eduard Zingerman
2024-08-22 1:20 ` Yonghong Song
2024-08-17 1:51 ` [PATCH bpf-next v2 3/5] bpf: support bpf_fastcall patterns for kfuncs Eduard Zingerman
2024-08-17 20:09 ` kernel test robot
2024-08-18 2:50 ` Eduard Zingerman
2024-08-22 1:23 ` Yonghong Song
2024-08-17 1:51 ` [PATCH bpf-next v2 4/5] bpf: allow bpf_fastcall for bpf_cast_to_kern_ctx and bpf_rdonly_cast Eduard Zingerman
2024-08-22 1:23 ` Yonghong Song
2024-08-17 1:51 ` [PATCH bpf-next v2 5/5] selftests/bpf: check if bpf_fastcall is recognized for kfuncs Eduard Zingerman
2024-08-22 1:38 ` Yonghong Song
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=b0cef1d8665baac74a173dbae37db884989b170b.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jose.marchesi@oracle.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/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