From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
christophe.leroy@csgroup.eu
Cc: sshegde@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
bigeasy@linutronix.de, will@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/1] powerpc: Enable dynamic preemption
Date: Tue, 11 Feb 2025 00:13:33 +0530 [thread overview]
Message-ID: <20250210184334.567383-1-sshegde@linux.ibm.com> (raw)
Now that preempt=lazy patches are merged upstream, sending out the
patch to support dynamic preemption based on DYNAMIC_KEY.
Once the arch supports static inline calls, it would be needed to
evaluate to see if that gives better performance.
This makes the same code for arm64 and powerpc. Will be sending an RFC
patch to move this static key into sched/core.
v3->v4:
- Use static key instead of using preempt_model_preemptible
(Sebastian Andrzej Siewior and Christophe Leroy)
- Dropped printing the preemption model, since it is addressed
in a patchset from Sebastian Andrzej Siewior
v2->v3:
- fixed a build error reported by linux test robot by including jump
label header.
v1->v2:
- Instead of copying asm-generic preempt.h content include it in
arch/asm preempt.h. (Christophe Leroy)
- Merge the patches into one patch (Christophe Leroy)
v3: https://lore.kernel.org/all/20250106051919.55020-1-sshegde@linux.ibm.com/
Shrikanth Hegde (1):
powerpc: enable dynamic preemption
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/preempt.h | 16 ++++++++++++++++
arch/powerpc/kernel/interrupt.c | 6 +++++-
arch/powerpc/lib/vmx-helper.c | 2 +-
4 files changed, 23 insertions(+), 2 deletions(-)
create mode 100644 arch/powerpc/include/asm/preempt.h
--
2.39.3
next reply other threads:[~2025-02-10 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 18:43 Shrikanth Hegde [this message]
2025-02-10 18:43 ` [PATCH v4 1/1] powerpc: enable dynamic preemption Shrikanth Hegde
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=20250210184334.567383-1-sshegde@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox