Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mete Durlu" <meted@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH] sched: Decouple PREFERRED_CPU from PARAVIRT
Date: Fri, 06 Nov 2026 12:48:08 +0000	[thread overview]
Message-ID: <sashiko-outbox-201413@kernel.org> (raw)
In-Reply-To: <20261106-preferredcpu-v1-1-3f0ca4944f8b@linux.ibm.com>

> PREFERRED_CPU mechanism does not rely on any feature introduced by PARAVIRT
> but PREFERRED_CPU still gated behind PARAVIRT. Any architecture that
> would like to enable PREFERRED_CPU mechanism has to also enable PARAVIRT
> and bring additional changes to accommodate PARAVIRT's requirements.
> 
> As an example, s390 doesn't enable PARAVIRT config for hardware virtualized
> Logical Partitions (LPAR). The steal time is accounted for the LPARs via
> architecture's own steal time accounting mechanism instead of the common
> steal time infrastructure PARAVIRT supplies.
> For s390 to enable PREFERRED_CPU, PRAVIRT and its required stubs are
> just unncessary.
> 
> Based on the discussion between Yury Norov and Peter Zijlstra over
> Yury's original patch [1]:
> 
> Introduce a new config flag HAVE_CPUTIME_STEAL to indicate that the
> architecture has steal time measurement capabilities already implemented
> and to signal that PARAVIRT is not required.
> Remove PARAVIRT gating from CPU_PREFERRED and add HAVE_CPUTIME_STEAL
> instead.
> Select HAVE_CPUTIME_STEAL for s390 and powerpc-pseries configs.
> 
> [1] https://lore.kernel.org/all/20261101192203.6979-2-ynorov@nvidia.com/
> 
> Reviewed-by: Yury Norov <ynorov@nvidia.com>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261106-preferredcpu-v1-1-3f0ca4944f8b@linux.ibm.com?part=1


  reply	other threads:[~2026-11-06 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 12:35 [PATCH] sched: Decouple PREFERRED_CPU from PARAVIRT Mete Durlu
2026-11-06 12:48 ` sashiko-bot [this message]
2026-11-06 16:15 ` 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=sashiko-outbox-201413@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=meted@linux.ibm.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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