From: Yury Norov <ynorov@nvidia.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Shrikanth Hegde <sshegde@linux.ibm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, juri.lelli@redhat.com,
yury.norov@gmail.com, kprateek.nayak@amd.com, iii@linux.ibm.com,
corbet@lwn.net, meted@linux.ibm.com, tglx@kernel.org,
gregkh@linuxfoundation.org, pbonzini@redhat.com,
seanjc@google.com, vschneid@redhat.com, huschle@linux.ibm.com,
rostedt@goodmis.org, 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 v11 05/12] sched/core: Try to use a preferred CPU in is_cpu_allowed
Date: Mon, 31 Aug 2026 12:53:44 -0400 [thread overview]
Message-ID: <apWxmL_brfi4fa4z@yury> (raw)
In-Reply-To: <CAKfTPtA5Bdw89hezn1wi_p0m0dJgJJ1GYg8H93PsvsMC4bVJxA@mail.gmail.com>
On Mon, Aug 31, 2026 at 05:09:41PM +0200, Vincent Guittot wrote:
> > Dietmar/Vincent,
> > Do you think it makes sense to enable the driver on ARM64 now?
> > Or you think it is better to delay it and once the feature is stable
> > ARM ecosystem can enable it?
>
> It's always better to support all arch by default, unless something is
> missing which is not the case here.
ARM64 testing is obviously missed.
next prev parent reply other threads:[~2026-08-31 16:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 10:38 [PATCH v11 00/12] sched, steal_governor: Introduce preferred CPUs and steal-driven vCPU backoff Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 01/12] sched/cputime: Add kcpustat_field_total helper Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 02/12] sched/docs: Document cpu_preferred_mask and Preferred CPU concept Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 03/12] cpumask: Introduce cpu_preferred_mask Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 04/12] sysfs: Add preferred CPU file Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 05/12] sched/core: Try to use a preferred CPU in is_cpu_allowed Shrikanth Hegde
2026-08-28 7:51 ` Dietmar Eggemann
2026-08-28 10:38 ` Vincent Guittot
2026-08-28 10:59 ` Shrikanth Hegde
2026-08-29 19:31 ` Yury Norov
2026-08-31 2:18 ` Shrikanth Hegde
2026-08-31 15:09 ` Vincent Guittot
2026-08-31 16:53 ` Yury Norov [this message]
2026-09-01 6:21 ` Vincent Guittot
2026-09-01 12:21 ` Dietmar Eggemann
2026-09-02 8:33 ` Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 06/12] sched/fair: Load balance only among preferred CPUs Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 07/12] sched/core: Push current task from non preferred CPU Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 08/12] sched/debug: Add migration stats due to non preferred CPUs Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 09/12] virt: Introduce steal governor driver Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 10/12] virt/steal_governor: Add control knobs for handling steal values Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 11/12] virt/steal_governor: Implement steal_governor policy loop Shrikanth Hegde
2026-08-25 10:38 ` [PATCH v11 12/12] virt/steal_governor: Enable the driver 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=apWxmL_brfi4fa4z@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.