BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, kernel-team@meta.com
Subject: Re: [PATCH v7 bpf-next 0/7] Allocate bpf trampoline on bpf_prog_pack
Date: Thu, 07 Dec 2023 01:40:25 +0000	[thread overview]
Message-ID: <170191322555.26401.9706369522702299505.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231206224054.492250-1-song@kernel.org>

Hello:

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

On Wed,  6 Dec 2023 14:40:47 -0800 you wrote:
> This set enables allocating bpf trampoline from bpf_prog_pack on x86. The
> majority of this work, however, is the refactoring of trampoline code.
> This is needed because we need to handle 4 archs and 2 users (trampoline
> and struct_ops).
> 
> 1/7 through 6/7 refactors trampoline code. A few helpers are added.
> 7/7 finally let bpf trampoline on x86 use bpf_prog_pack.
> 
> [...]

Here is the summary with links:
  - [v7,bpf-next,1/7] bpf: Let bpf_prog_pack_free handle any pointer
    https://git.kernel.org/bpf/bpf-next/c/f08a1c658257
  - [v7,bpf-next,2/7] bpf: Adjust argument names of arch_prepare_bpf_trampoline()
    https://git.kernel.org/bpf/bpf-next/c/7a3d9a159b17
  - [v7,bpf-next,3/7] bpf: Add helpers for trampoline image management
    https://git.kernel.org/bpf/bpf-next/c/82583daa2efc
  - [v7,bpf-next,4/7] bpf, x86: Adjust arch_prepare_bpf_trampoline return value
    https://git.kernel.org/bpf/bpf-next/c/38b8b58ae776
  - [v7,bpf-next,5/7] bpf: Add arch_bpf_trampoline_size()
    https://git.kernel.org/bpf/bpf-next/c/96d1b7c081c0
  - [v7,bpf-next,6/7] bpf: Use arch_bpf_trampoline_size
    https://git.kernel.org/bpf/bpf-next/c/26ef208c209a
  - [v7,bpf-next,7/7] x86, bpf: Use bpf_prog_pack for bpf trampoline
    https://git.kernel.org/bpf/bpf-next/c/3ba026fca878

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



      parent reply	other threads:[~2023-12-07  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:40 [PATCH v7 bpf-next 0/7] Allocate bpf trampoline on bpf_prog_pack Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 1/7] bpf: Let bpf_prog_pack_free handle any pointer Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 2/7] bpf: Adjust argument names of arch_prepare_bpf_trampoline() Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 3/7] bpf: Add helpers for trampoline image management Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 4/7] bpf, x86: Adjust arch_prepare_bpf_trampoline return value Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 5/7] bpf: Add arch_bpf_trampoline_size() Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 6/7] bpf: Use arch_bpf_trampoline_size Song Liu
2023-12-06 22:40 ` [PATCH v7 bpf-next 7/7] x86, bpf: Use bpf_prog_pack for bpf trampoline Song Liu
2023-12-07  1: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=170191322555.26401.9706369522702299505.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=kernel-team@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=song@kernel.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