All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH bpf-next 0/3] s390/bpf: Use kernel's expoline thunks
Date: Mon, 19 May 2025 23:30:03 +0100	[thread overview]
Message-ID: <20250519223646.66382-1-iii@linux.ibm.com> (raw)

Hi,

This series simplifies the s390 JIT by replacing the generation of
expolines (Spectre mitigation) with using the ones from the kernel
text. This is possible thanks to the V!=R s390 kernel rework.
Patch 1 is a small prerequisite for arch/s390 that I would like to
get in via the BPF tree. It has Heiko's Acked-by.
Patches 2 and 3 are the implementation.

Best regards,
Ilya

Ilya Leoshkevich (3):
  s390: always declare expoline thunks
  s390/bpf: Add macros for calling external functions
  s390/bpf: Use kernel's expoline thunks

 arch/s390/include/asm/nospec-branch.h |   4 -
 arch/s390/net/bpf_jit_comp.c          | 121 +++++++++++++-------------
 2 files changed, 59 insertions(+), 66 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-19 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 22:30 Ilya Leoshkevich [this message]
2025-05-19 22:30 ` [PATCH bpf-next 1/3] s390: always declare expoline thunks Ilya Leoshkevich
2025-05-19 22:30 ` [PATCH bpf-next 2/3] s390/bpf: Add macros for calling external functions Ilya Leoshkevich
2025-05-19 22:30 ` [PATCH bpf-next 3/3] s390/bpf: Use kernel's expoline thunks Ilya Leoshkevich
2025-05-22 15:50 ` [PATCH bpf-next 0/3] " patchwork-bot+netdevbpf

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=20250519223646.66382-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.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 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.