All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Khmelevskii <max@linux.ibm.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	bpf@vger.kernel.org, iii@linux.ibm.com, hca@linux.ibm.com,
	gor@linux.ibm.com, agordeev@linux.ibm.com
Subject: Re: [PATCH bpf-next] s390/bpf: inline smp_processor_id and current_task
Date: Tue, 21 Apr 2026 23:00:05 +0000	[thread overview]
Message-ID: <177681240559.3038431.3671881704528464406.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260414142930.528751-1-max@linux.ibm.com>

Hello:

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

On Tue, 14 Apr 2026 16:29:26 +0200 you wrote:
> Inline these calls in bpf jit:
>  - bpf_get_smp_processor_id()
>  - bpf_get_current_task()
>  - bpf_get_current_task_btf()
> 
> s390 has a 8 KiB per-CPU prefix area in the CPU's
> virtual address space, called the lowcore. It is a
> struct that contains the cpu number and a pointer
> to the current task. These are exactly the values
> returned by the BPF helpers.
> 
> [...]

Here is the summary with links:
  - [bpf-next] s390/bpf: inline smp_processor_id and current_task
    https://git.kernel.org/bpf/bpf-next/c/9012cf2491e3

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



      reply	other threads:[~2026-04-21 23:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 14:29 [PATCH bpf-next] s390/bpf: inline smp_processor_id and current_task Maxim Khmelevskii
2026-04-21 23: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=177681240559.3038431.3671881704528464406.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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 \
    --cc=iii@linux.ibm.com \
    --cc=max@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.