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, jose.marchesi@oracle.com
Subject: Re: [PATCH bpf-next v4 00/10] no_caller_saved_registers attribute for helper calls
Date: Wed, 24 Jul 2024 04:00:44 +0000	[thread overview]
Message-ID: <172179364482.1919.9590705031832457529.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240722233844.1406874-1-eddyz87@gmail.com>

Hello:

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

On Mon, 22 Jul 2024 16:38:34 -0700 you wrote:
> This patch-set seeks to allow using no_caller_saved_registers gcc/clang
> attribute with some BPF helper functions (and kfuncs in the future).
> 
> As documented in [1], this attribute means that function scratches
> only some of the caller saved registers defined by ABI.
> For BPF the set of such registers could be defined as follows:
> - R0 is scratched only if function is non-void;
> - R1-R5 are scratched only if corresponding parameter type is defined
>   in the function prototype.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,01/10] bpf: add a get_helper_proto() utility function
    https://git.kernel.org/bpf/bpf-next/c/19b0934f0b13
  - [bpf-next,v4,02/10] bpf: no_caller_saved_registers attribute for helper calls
    https://git.kernel.org/bpf/bpf-next/c/c473f709550f
  - [bpf-next,v4,03/10] bpf, x86, riscv, arm: no_caller_saved_registers for bpf_get_smp_processor_id()
    https://git.kernel.org/bpf/bpf-next/c/a5a0f95ba4e9
  - [bpf-next,v4,04/10] selftests/bpf: extract utility function for BPF disassembly
    https://git.kernel.org/bpf/bpf-next/c/67b1c158c54e
  - [bpf-next,v4,05/10] selftests/bpf: print correct offset for pseudo calls in disasm_insn()
    https://git.kernel.org/bpf/bpf-next/c/9f3e5a694b03
  - [bpf-next,v4,06/10] selftests/bpf: no need to track next_match_pos in struct test_loader
    https://git.kernel.org/bpf/bpf-next/c/0bbaa40df698
  - [bpf-next,v4,07/10] selftests/bpf: extract test_loader->expect_msgs as a data structure
    https://git.kernel.org/bpf/bpf-next/c/a70c32d65ec7
  - [bpf-next,v4,08/10] selftests/bpf: allow checking xlated programs in verifier_* tests
    https://git.kernel.org/bpf/bpf-next/c/69c992268830
  - [bpf-next,v4,09/10] selftests/bpf: __arch_* macro to limit test cases to specific archs
    https://git.kernel.org/bpf/bpf-next/c/c64d2f72bf2e
  - [bpf-next,v4,10/10] selftests/bpf: test no_caller_saved_registers spill/fill removal
    https://git.kernel.org/bpf/bpf-next/c/2daa48f6e400

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-07-24  4:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 23:38 [PATCH bpf-next v4 00/10] no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 01/10] bpf: add a get_helper_proto() utility function Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 02/10] bpf: no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 03/10] bpf, x86, riscv, arm: no_caller_saved_registers for bpf_get_smp_processor_id() Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 04/10] selftests/bpf: extract utility function for BPF disassembly Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 05/10] selftests/bpf: print correct offset for pseudo calls in disasm_insn() Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 06/10] selftests/bpf: no need to track next_match_pos in struct test_loader Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 07/10] selftests/bpf: extract test_loader->expect_msgs as a data structure Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 08/10] selftests/bpf: allow checking xlated programs in verifier_* tests Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 09/10] selftests/bpf: __arch_* macro to limit test cases to specific archs Eduard Zingerman
2024-07-22 23:38 ` [PATCH bpf-next v4 10/10] selftests/bpf: test no_caller_saved_registers spill/fill removal Eduard Zingerman
2024-07-23  0:36 ` [PATCH bpf-next v4 00/10] no_caller_saved_registers attribute for helper calls bot+bpf-ci
2024-07-23  1:18 ` bot+bpf-ci
2024-07-23  2:42 ` bot+bpf-ci
2024-07-24  3:52 ` Alexei Starovoitov
2024-07-24  4:00 ` 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=172179364482.1919.9590705031832457529.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=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