mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yury Norov <ynorov@nvidia.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Shrikanth Hegde <sshegde@linux.ibm.com>,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, yury.norov@gmail.com,
	kprateek.nayak@amd.com, iii@linux.ibm.com, corbet@lwn.net,
	tglx@kernel.org, gregkh@linuxfoundation.org, pbonzini@redhat.com,
	seanjc@google.com, vschneid@redhat.com, huschle@linux.ibm.com,
	rostedt@goodmis.org, dietmar.eggemann@arm.com,
	maddy@linux.ibm.com, srikar@linux.ibm.com, hdanton@sina.com,
	chleroy@kernel.org, vineeth@bitbyteword.org, frederic@kernel.org,
	arighi@nvidia.com, pauld@redhat.com, christian.loehle@arm.com,
	tj@kernel.org, tommaso.cucinotta@gmail.com, maz@kernel.org,
	rafael@kernel.org, rdunlap@infradead.org, kernellwp@gmail.com,
	linux-doc@vger.kernel.org, jgross@suse.com,
	virtualization@lists.linux.dev, sunlightlinux@gmail.com
Subject: Re: [PATCH v14 04/13] cpumask: Introduce cpu_preferred_mask
Date: Thu, 29 Oct 2026 12:39:37 -0400	[thread overview]
Message-ID: <auN2yRZPKKWYk_CP@yury> (raw)
In-Reply-To: <b83e2d2f-681d-4e19-a680-c076493b3edd@linux.ibm.com>

On Thu, Oct 29, 2026 at 05:36:28PM +0100, Mete Durlu wrote:
> On 29/10/2026 17:28, Yury Norov wrote:
> > On Thu, Oct 29, 2026 at 02:32:08PM +0100, Mete Durlu wrote:
> > > On 28/09/2026 07:37, Shrikanth Hegde wrote:
> > > > Provide the preferred CPU infrastructure. Define get/set macros
> > > > which could be used to get/set CPU state as preferred.
> > > > 
> > > > CONFIG_PREFERRED_CPU will be selected by the driver which handles
> > > > steal time values. It is going to set/clear preferred CPU state.
> > > > This driver will be called steal_governor and it is introduced in
> > > > subsequent patches. It periodically computes the steal ratio and
> > > > decides on preferred CPU state.
> > > > 
> > > > A CPU is set to preferred when it becomes active. Later it may be
> > > > marked as non-preferred depending on steal ratio by the steal_governor.
> > > > 
> > > > Always maintain design construct of preferred is subset of active.
> > > > i.e. preferred ⊆ active ⊆ online ⊆ present ⊆ possible
> > > > 
> > > > With CONFIG_PREFERRED_CPU=n, ensure set_cpu_preferred is a nop and get
> > > > method returns the active state in that case.
> > > > 
> > > > Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
> > > > ---
> > > >    include/linux/cpumask.h | 24 ++++++++++++++++++++++++
> > > >    kernel/Kconfig.preempt  |  4 ++++
> > > >    kernel/cpu.c            |  6 ++++++
> > > >    kernel/sched/core.c     |  5 +++++
> > > >    4 files changed, 39 insertions(+)
> > > 
> > > [..snip..]
> > > 
> > > >    #define cpu_is_offline(cpu)	unlikely(!cpu_online(cpu))
> > > > diff --git a/kernel/Kconfig.preempt b/kernel/Kconfig.preempt
> > > > index 985aea617cfe..edc067a0c422 100644
> > > > --- a/kernel/Kconfig.preempt
> > > > +++ b/kernel/Kconfig.preempt
> > > > @@ -194,3 +194,7 @@ config SCHED_CLASS_EXT
> > > >    	  For more information:
> > > >    	    Documentation/scheduler/sched-ext.rst
> > > >    	    https://github.com/sched-ext/scx
> > > > +
> > > > +config PREFERRED_CPU
> > > > +	bool
> > > > +	depends on SMP && PARAVIRT
> > > FWICT, PREFERRED_CPU mechanism can work perfectly fine without PARAVIRT
> > > selected. It would be annoying to enable it and implement a dummy
> > > paravirt_steal_clock() just for that.
> > > 
> > > Shrikanth, would it be possible to drop that dependency?
> > 
> > Do you have a non-paravirt case in mind?
> 
> s390 LPARs are exactly that. s390 does not select PARAVIRT by default
> but enabling PREFERRED_CPU is strongly considered.
> 
> I removed the PARAVIRT dependency and gave the whole thing a quick
> spin. Builds and functions w/o any issues on s390!
> > I'm actually about to submit an RFC that drops the PARAVIRT dependency
> > and provides write access to the preferred mask. But I want to make
> > sure that we need it, and we've got no reasonable mechanism to put
> > unneeded CPUs on idle already.
> 
> You can mention s390 LPARs as valid case on your RFC if need be.

Sure, will do. I'm about submitting this before the end of week; will
add you in CC.

Thanks,
Yury

  reply	other threads:[~2026-10-29 16:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  5:37 [PATCH v14 00/13] sched, steal_governor: Introduce preferred CPUs and steal-driven vCPU backoff Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 01/13] sched/cputime: Add kcpustat_field_total helper Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 02/13] cpumask: Introduce cpumask_intersects_and Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 03/13] sched/docs: Document cpu_preferred_mask and Preferred CPU concept Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 04/13] cpumask: Introduce cpu_preferred_mask Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-10-29 13:32   ` [PATCH v14 04/13] " Mete Durlu
2026-10-29 16:28     ` Yury Norov
2026-10-29 16:36       ` Mete Durlu
2026-10-29 16:39         ` Yury Norov [this message]
2026-09-28  5:37 ` [PATCH v14 05/13] sysfs: Add preferred CPU file Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 06/13] sched/core: Try to use a preferred CPU in is_cpu_allowed Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 07/13] sched/fair: Load balance only among preferred CPUs Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 08/13] sched/core: Push current task from non preferred CPU Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 09/13] sched/debug: Add migration stats due to non preferred CPUs Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-29 12:18   ` [PATCH v14 09/13] " Nathan Chancellor
2026-09-29 12:43     ` Shrikanth Hegde
2026-09-29 14:57       ` Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 10/13] virt: Introduce steal governor driver Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 11/13] virt/steal_governor: Add control knobs for handling steal values Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 12/13] virt/steal_governor: Implement steal_governor policy loop Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for Shrikanth Hegde
2026-09-28  5:37 ` [PATCH v14 13/13] virt/steal_governor: Enable the driver Shrikanth Hegde
2026-09-28  7:01   ` [tip: sched/core] " tip-bot2 for 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=auN2yRZPKKWYk_CP@yury \
    --to=ynorov@nvidia.com \
    --cc=arighi@nvidia.com \
    --cc=chleroy@kernel.org \
    --cc=christian.loehle@arm.com \
    --cc=corbet@lwn.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=frederic@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=huschle@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=jgross@suse.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernellwp@gmail.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=maz@kernel.org \
    --cc=meted@linux.ibm.com \
    --cc=mingo@kernel.org \
    --cc=pauld@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=seanjc@google.com \
    --cc=srikar@linux.ibm.com \
    --cc=sshegde@linux.ibm.com \
    --cc=sunlightlinux@gmail.com \
    --cc=tglx@kernel.org \
    --cc=tj@kernel.org \
    --cc=tommaso.cucinotta@gmail.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vineeth@bitbyteword.org \
    --cc=virtualization@lists.linux.dev \
    --cc=vschneid@redhat.com \
    --cc=yury.norov@gmail.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

all inboxes | Powered by JetHome®