BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v3 0/6] support bpf_fastcall patterns for calls to kfuncs
Date: Thu, 22 Aug 2024 15:40:41 +0000	[thread overview]
Message-ID: <172434124150.2363434.3255650666548464904.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822084112.3257995-1-eddyz87@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 22 Aug 2024 01:41:06 -0700 you wrote:
> As an extension of [1], allow bpf_fastcall patterns for kfuncs:
> - pattern rules are the same as for helpers;
> - spill/fill removal is allowed only for kfuncs listed in the
>   is_fastcall_kfunc_call (under assumption that such kfuncs would
>   always be members of special_kfunc_list).
> 
> Allow bpf_fastcall rewrite for bpf_cast_to_kern_ctx() and
> bpf_rdonly_cast() in order to conjure selftests for this feature.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/6] bpf: rename nocsr -> bpf_fastcall in verifier
    https://git.kernel.org/bpf/bpf-next/c/ae010757a55b
  - [bpf-next,v3,2/6] selftests/bpf: rename nocsr -> bpf_fastcall in selftests
    https://git.kernel.org/bpf/bpf-next/c/adec67d372fe
  - [bpf-next,v3,3/6] bpf: support bpf_fastcall patterns for kfuncs
    https://git.kernel.org/bpf/bpf-next/c/b2ee6d27e9c6
  - [bpf-next,v3,4/6] bpf: allow bpf_fastcall for bpf_cast_to_kern_ctx and bpf_rdonly_cast
    https://git.kernel.org/bpf/bpf-next/c/40609093247b
  - [bpf-next,v3,5/6] selftests/bpf: by default use arch mask allowing all archs
    https://git.kernel.org/bpf/bpf-next/c/f406026fefa7
  - [bpf-next,v3,6/6] selftests/bpf: check if bpf_fastcall is recognized for kfuncs
    https://git.kernel.org/bpf/bpf-next/c/8c2e043daada

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-08-22 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  8:41 [PATCH bpf-next v3 0/6] support bpf_fastcall patterns for calls to kfuncs Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 1/6] bpf: rename nocsr -> bpf_fastcall in verifier Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 2/6] selftests/bpf: rename nocsr -> bpf_fastcall in selftests Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 3/6] bpf: support bpf_fastcall patterns for kfuncs Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 4/6] bpf: allow bpf_fastcall for bpf_cast_to_kern_ctx and bpf_rdonly_cast Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 5/6] selftests/bpf: by default use arch mask allowing all archs Eduard Zingerman
2024-08-22  8:41 ` [PATCH bpf-next v3 6/6] selftests/bpf: check if bpf_fastcall is recognized for kfuncs Eduard Zingerman
2024-08-22 15:40 ` patchwork-bot+netdevbpf [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=172434124150.2363434.3255650666548464904.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.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