From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kernel-team@fb.com,
x86@kernel.org
Subject: Re: [PATCH v5 bpf-next 5/7] x86/alternative: introduce text_poke_copy
Date: Fri, 21 Jan 2022 10:52:36 +0100 [thread overview]
Message-ID: <20220121095236.GD20638@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220120191306.1801459-6-song@kernel.org>
On Thu, Jan 20, 2022 at 11:13:03AM -0800, Song Liu wrote:
> This will be used by BPF jit compiler to dump JITed binary to a RX huge
> page, and thus allow multiple BPF programs sharing the a huge (2MB) page.
>
> Signed-off-by: Song Liu <song@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2022-01-21 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 19:12 [PATCH v5 bpf-next 0/7] bpf_prog_pack allocator Song Liu
2022-01-20 19:12 ` [PATCH v5 bpf-next 1/7] x86/Kconfig: select HAVE_ARCH_HUGE_VMALLOC with HAVE_ARCH_HUGE_VMAP Song Liu
2022-01-20 19:13 ` [PATCH v5 bpf-next 2/7] bpf: use bytes instead of pages for bpf_jit_[charge|uncharge]_modmem Song Liu
2022-01-20 19:13 ` [PATCH v5 bpf-next 3/7] bpf: use size instead of pages in bpf_binary_header Song Liu
2022-01-20 19:13 ` [PATCH v5 bpf-next 4/7] bpf: add a pointer of bpf_binary_header to bpf_prog Song Liu
2022-01-20 19:13 ` [PATCH v5 bpf-next 5/7] x86/alternative: introduce text_poke_copy Song Liu
2022-01-21 9:52 ` Peter Zijlstra [this message]
2022-01-20 19:13 ` [PATCH v5 bpf-next 6/7] bpf: introduce bpf_prog_pack allocator Song Liu
2022-01-20 19:13 ` [PATCH v5 bpf-next 7/7] bpf, x86_64: use " Song Liu
2022-01-21 4:59 ` Alexei Starovoitov
2022-01-21 17:53 ` Song Liu
2022-01-21 18:29 ` Alexei Starovoitov
2022-01-21 18:56 ` Song Liu
2022-01-21 1:06 ` [PATCH v5 bpf-next 0/7] " Song Liu
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=20220121095236.GD20638@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=song@kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.