linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Mark Rutland <mark.rutland@arm.com>,
	catalin.marinas@arm.com, will@kernel.org, maddy@linux.ibm.com
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, tglx@linutronix.de,
	bigeasy@linutronix.de, vschneid@redhat.com,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] sched: preempt: Move dynamic keys into kernel/sched
Date: Sun, 13 Jul 2025 10:20:25 +0530	[thread overview]
Message-ID: <3de6a9db-a122-420d-a845-2087136a0d6c@linux.ibm.com> (raw)
In-Reply-To: <aFBIPxOGbWfTCWLm@J2N7QTR9R3>


> On Tue, Jun 10, 2025 at 01:23:44PM +0530, Shrikanth Hegde wrote:
>> Dynamic preemption can be static key or static call based.
>> Static key is used to check kernel preemption depending on
>> the current preemption model. i.e enable for lazy, full.
>>
>> Code is spread currently across entry/common.c, arm64 and latest being
>> powerpc. There is little arch specific to it. For example, arm64,
>> powerpc does the same thing. It is better to move it into kernel/sched
>> since preemption is more closely associated with scheduler.
>>
>> Plus, Any new arch that wants dynamic preemption enabled need to have
>> only HAVE_PREEMPT_DYNAMIC_KEY.
>>
>> This is more of code movement. No functional change.
>>
>> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> 
> I've tested this on arm64 atop v6.16-rc2, building and booting defconfig
> and defconfig + PREEMPT_DYNAMIC=y.
> 

Hi Mark. Thanks for testing it. Sorry for delayed response.

> It builds cleanly, boots fine, and I think this is obviously correct
> given it's just moving things around, so FWIW:
> 
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> 
> Catalin, Will, are you happy with this?
>

Thank you will for the tags.


> I assume this would go via the tip tree?
> 

Maddy, are you okay with this?

I would request it to go via tip tree.

  reply	other threads:[~2025-07-13  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  7:53 [PATCH 0/1] powerpc, arm64: move preempt dynamic key into kernel/sched Shrikanth Hegde
2025-06-10  7:53 ` [PATCH 1/1] sched: preempt: Move dynamic keys " Shrikanth Hegde
2025-06-13  9:49   ` Shrikanth Hegde
2025-06-16 16:37   ` Mark Rutland
2025-07-13  4:50     ` Shrikanth Hegde [this message]
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=3de6a9db-a122-420d-a845-2087136a0d6c@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).