From: Daniel Borkmann <daniel@iogearbox.net>
To: Catalin Marinas <catalin.marinas@arm.com>,
Puranjay Mohan <puranjay12@gmail.com>
Cc: ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, mark.rutland@arm.com, bpf@vger.kernel.org,
kpsingh@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xukuohai@huaweicloud.com
Subject: Re: [PATCH bpf-next v8 0/2] bpf, arm64: use BPF prog pack allocator in BPF JIT
Date: Wed, 28 Feb 2024 14:34:54 +0100 [thread overview]
Message-ID: <7b4588ff-c769-c185-3b4c-aab4a472d872@iogearbox.net> (raw)
In-Reply-To: <Zd8o__ow2F6-ENVh@arm.com>
On 2/28/24 1:37 PM, Catalin Marinas wrote:
> On Wed, Feb 21, 2024 at 02:51:04PM +0000, Puranjay Mohan wrote:
>> Puranjay Mohan (2):
>> arm64: patching: implement text_poke API
>> bpf, arm64: use bpf_prog_pack for memory management
>>
>> arch/arm64/include/asm/patching.h | 2 +
>> arch/arm64/kernel/patching.c | 75 ++++++++++++++++
>> arch/arm64/net/bpf_jit_comp.c | 139 ++++++++++++++++++++++++------
>> 3 files changed, 192 insertions(+), 24 deletions(-)
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>
> Feel free to take it through the bpf tree.
Thanks for the review, Catalin!
Puranjay, this needs a rebase before it can be merged into bpf-next,
please take a look and resubmit.
next prev parent reply other threads:[~2024-02-28 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 14:51 [PATCH bpf-next v8 0/2] bpf, arm64: use BPF prog pack allocator in BPF JIT Puranjay Mohan
2024-02-21 14:51 ` [PATCH bpf-next v8 1/2] arm64: patching: implement text_poke API Puranjay Mohan
2024-02-21 14:51 ` [PATCH bpf-next v8 2/2] bpf, arm64: use bpf_prog_pack for memory management Puranjay Mohan
2024-02-28 12:37 ` [PATCH bpf-next v8 0/2] bpf, arm64: use BPF prog pack allocator in BPF JIT Catalin Marinas
2024-02-28 13:34 ` Daniel Borkmann [this message]
2024-02-28 14:20 ` Puranjay Mohan
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=7b4588ff-c769-c185-3b4c-aab4a472d872@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=puranjay12@gmail.com \
--cc=song@kernel.org \
--cc=xukuohai@huaweicloud.com \
/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;
as well as URLs for NNTP newsgroup(s).