public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, adubey@linux.ibm.com
Cc: hbathini@linux.ibm.com, bpf@vger.kernel.org, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, shuah@kernel.org,
	linux-kselftest@vger.kernel.org,
	Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Subject: Re: [PATCH v7 1/2] powerpc64/bpf: Implement JIT support for private stack
Date: Wed,  8 Apr 2026 09:58:13 +0530	[thread overview]
Message-ID: <177562236435.1381144.14761242301174081744.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260401103215.104438-1-adubey@linux.ibm.com>

On Wed, 01 Apr 2026 06:32:14 -0400, adubey@linux.ibm.com wrote:
> Provision the private stack as a per-CPU allocation during
> bpf_int_jit_compile(). Align the stack to 16 bytes and place guard
> regions at both ends to detect runtime stack overflow and underflow.
> 
> Round the private stack size up to the nearest 16-byte boundary.
> Make each guard region 16 bytes to preserve the required overall
> 16-byte alignment. When private stack is set, skip bpf stack size
> accounting in kernel stack.
> 
> [...]

Applied to powerpc/next.

[1/2] powerpc64/bpf: Implement JIT support for private stack
      https://git.kernel.org/powerpc/c/156d985123b6d6e5189cfd0286b93c12167ae798
[2/2] selftests/bpf: Enable private stack tests for powerpc64
      https://git.kernel.org/powerpc/c/e640bcd1bf83dbdaa967b20cd98a782d52ec89cf

cheers


      parent reply	other threads:[~2026-04-08  4:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 10:32 [PATCH v7 1/2] powerpc64/bpf: Implement JIT support for private stack adubey
2026-04-01 10:32 ` [PATCH v7 2/2] selftests/bpf: Enable private stack tests for powerpc64 adubey
2026-04-08  4:28 ` 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=177562236435.1381144.14761242301174081744.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=linux-kselftest@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=shuah@kernel.org \
    --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