From: sashiko-bot@kernel.org
To: "Shrikanth Hegde" <sshegde@linux.ibm.com>
Cc: "Eugenio Perez" <eperezma@redhat.com>,
virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v14 10/13] virt: Introduce steal governor driver
Date: Mon, 28 Sep 2026 05:47:35 +0000 [thread overview]
Message-ID: <20260928054735.95FFD1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260928053728.797539-11-sshegde@linux.ibm.com>
> Introduce a new driver in virt named steal_governor. This driver
> will compute the steal time and drive the policy decisions regarding the
> preferred CPU state.
>
> Note that this driver is strictly intended for actual guests. Hence
> block it on Xen dom0.
> More details can be found in Documentation/driver-api/steal-governor.rst.
>
> A new kconfig called STEAL_GOVERNOR is introduced in subsequent patches,
> which enables this driver. This driver will select CONFIG_PREFERRED_CPU.
> This makes configs driven by user preference/configuration.
> When the driver is disabled, preferred CPUs remain the same as active CPUs.
>
> The file layout of the driver is kept simple for now. The code is in
> drivers/virt/steal_governor.c, and the configs are part of
> drivers/virt/Kconfig.
>
> The main structure of the steal governor contains:
> - work, delay: Deferred periodic work function variables.
> - steal, time: Used to calculate deltas during periodic work.
> - interval_ms, high_threshold, low_threshold: Tuning knobs for the
> steal governor.
>
> While there, add MAINTAINERS entry for this new driver.
>
> Suggested-by: Yury Norov <yury.norov@gmail.com>
> Suggested-by: K Prateek Nayak <kprateek.nayak@amd.com>
> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260928053728.797539-1-sshegde@linux.ibm.com?part=10
next prev parent reply other threads:[~2026-09-28 5:47 UTC|newest]
Thread overview: 32+ 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 5:54 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 02/13] cpumask: Introduce cpumask_intersects_and Shrikanth Hegde
2026-09-28 5:44 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 03/13] sched/docs: Document cpu_preferred_mask and Preferred CPU concept Shrikanth Hegde
2026-09-28 5:42 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 04/13] cpumask: Introduce cpu_preferred_mask Shrikanth Hegde
2026-09-28 5:46 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 05/13] sysfs: Add preferred CPU file Shrikanth Hegde
2026-09-28 5:47 ` sashiko-bot
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 6:00 ` sashiko-bot
2026-09-28 6:48 ` Shrikanth Hegde
2026-09-28 5:37 ` [PATCH v14 07/13] sched/fair: Load balance only among preferred CPUs Shrikanth Hegde
2026-09-28 5:55 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 08/13] sched/core: Push current task from non preferred CPU Shrikanth Hegde
2026-09-28 5:56 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 09/13] sched/debug: Add migration stats due to non preferred CPUs Shrikanth Hegde
2026-09-28 5:48 ` sashiko-bot
2026-09-29 12:18 ` 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 5:47 ` sashiko-bot [this message]
2026-09-28 5:37 ` [PATCH v14 11/13] virt/steal_governor: Add control knobs for handling steal values Shrikanth Hegde
2026-09-28 5:46 ` sashiko-bot
2026-09-28 5:37 ` [PATCH v14 12/13] virt/steal_governor: Implement steal_governor policy loop Shrikanth Hegde
2026-09-28 5:51 ` sashiko-bot
2026-09-28 6:52 ` Shrikanth Hegde
2026-09-28 5:37 ` [PATCH v14 13/13] virt/steal_governor: Enable the driver Shrikanth Hegde
2026-09-28 5:48 ` sashiko-bot
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=20260928054735.95FFD1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sshegde@linux.ibm.com \
--cc=virtualization@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 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.