From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, maddy@linux.ibm.com
Cc: sshegde@linux.ibm.com, tglx@linutronix.de, bigeasy@linutronix.de,
vschneid@redhat.com, dietmar.eggemann@arm.com,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com
Subject: [PATCH 0/1] powerpc, arm64: move preempt dynamic key into kernel/sched
Date: Tue, 10 Jun 2025 13:23:43 +0530 [thread overview]
Message-ID: <20250610075344.1379597-1-sshegde@linux.ibm.com> (raw)
Current usage of preempt dynamic key is not specific to architecture and
can be moved into sched/core instead. Most of the code around it looks
similar. (same code for powerpc, arm64).
Since preemption is more associated with scheduler rather than
entry/exit, it is probably better that they should be moved.
This is tested on powerVM PREEMPT_DYNAMIC=y/n.
Only Compile tested on arm64. It would be great if someone can test both
PREEMPT_DYNAMIC=y/n configs there.
Shrikanth Hegde (1):
sched: preempt: Move dynamic keys into kernel/sched
arch/arm64/include/asm/preempt.h | 1 -
arch/arm64/kernel/entry-common.c | 8 --------
arch/powerpc/include/asm/preempt.h | 16 ----------------
arch/powerpc/kernel/interrupt.c | 4 ----
include/linux/entry-common.h | 1 -
include/linux/sched.h | 8 ++++++++
kernel/entry/common.c | 1 -
kernel/sched/core.c | 4 ++++
8 files changed, 12 insertions(+), 31 deletions(-)
delete mode 100644 arch/powerpc/include/asm/preempt.h
--
2.43.0
next reply other threads:[~2025-06-10 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 7:53 Shrikanth Hegde [this message]
2025-06-10 7:53 ` [PATCH 1/1] sched: preempt: Move dynamic keys into kernel/sched Shrikanth Hegde
2025-06-13 9:49 ` Shrikanth Hegde
2025-06-16 16:37 ` Mark Rutland
2025-07-13 4:50 ` Shrikanth Hegde
2025-07-11 14:56 ` Will Deacon
2025-07-14 2:39 ` Madhavan Srinivasan
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=20250610075344.1379597-1-sshegde@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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;
as well as URLs for NNTP newsgroup(s).