public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Hari Bathini <hbathini@linux.ibm.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Saket Kumar Bhaskar <skb99@linux.ibm.com>,
	Abhishek Dubey <adubey@linux.ibm.com>,
	Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Subject: Re: [PATCH v4 0/6] powerpc64/bpf: various fixes
Date: Wed, 11 Mar 2026 07:44:01 +0530	[thread overview]
Message-ID: <177319508345.269267.12670103641877227517.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260303181031.390073-1-hbathini@linux.ibm.com>

On Tue, 03 Mar 2026 23:40:24 +0530, Hari Bathini wrote:
> List of fixes for powerpc64 BPF JIT:
> - Patches 1, 2 & 6 fix issues with existing powerpc64 JIT and are
>   tagged for -stable.
> - Patches 3 & 4 resolve issues with bpf2bpf tailcall support added
>   recently.
> - Patch 5 resolves an issue reported by bot+bpf-ci@kernel.org while
>   adding exceptions support on powerpc64 BPF JIT.
> 
> [...]

Applied to powerpc/fixes.

[1/6] powerpc64/bpf: do not increment tailcall count when prog is NULL
      https://git.kernel.org/powerpc/c/521bd39d9d28ce54cbfec7f9b89c94ad4fdb8350
[2/6] powerpc64/bpf: fix the address returned by bpf_get_func_ip
      https://git.kernel.org/powerpc/c/157820264ac3dadfafffad63184b883eb28f9ae0
[3/6] powerpc64/bpf: use consistent tailcall offset in trampoline
      https://git.kernel.org/powerpc/c/3727d6ec13665c1d99bf6dedb107104368ba42b4
[4/6] powerpc64/bpf: remove BPF redzone protection in trampoline stack
      https://git.kernel.org/powerpc/c/2d347d10f8e20e28a9eab52edf55079ae1ec0aae
[5/6] powerpc64/bpf: fix handling of BPF stack in exception callback
      https://git.kernel.org/powerpc/c/51b8de4b3d27ec12128fa2405e526c527a77ae65
[6/6] powerpc64/bpf: fix kfunc call support
      https://git.kernel.org/powerpc/c/01b6ac72729610ae732ca2a66e3a642e23f6cd60

cheers


      parent reply	other threads:[~2026-03-11  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 18:10 [PATCH v4 0/6] powerpc64/bpf: various fixes Hari Bathini
2026-03-03 18:10 ` [PATCH v4 1/6] powerpc64/bpf: do not increment tailcall count when prog is NULL Hari Bathini
2026-03-03 18:10 ` [PATCH v4 2/6] powerpc64/bpf: fix the address returned by bpf_get_func_ip Hari Bathini
2026-03-03 18:10 ` [PATCH v4 3/6] powerpc64/bpf: use consistent tailcall offset in trampoline Hari Bathini
2026-03-03 18:10 ` [PATCH v4 4/6] powerpc64/bpf: remove BPF redzone protection in trampoline stack Hari Bathini
2026-03-03 18:10 ` [PATCH v4 5/6] powerpc64/bpf: fix handling of BPF stack in exception callback Hari Bathini
2026-03-03 18:10 ` [PATCH v4 6/6] powerpc64/bpf: fix kfunc call support Hari Bathini
2026-03-11  2:14 ` Madhavan Srinivasan [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=177319508345.269267.12670103641877227517.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=adubey@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=hbathini@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=skb99@linux.ibm.com \
    --cc=venkat88@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox