From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, tglx@linutronix.de,
yury.norov@gmail.com, maddy@linux.ibm.com, srikar@linux.ibm.com,
pbonzini@redhat.com, seanjc@google.com, kprateek.nayak@amd.com,
vschneid@redhat.com, iii@linux.ibm.com, huschle@linux.ibm.com,
rostedt@goodmis.org, dietmar.eggemann@arm.com,
christophe.leroy@csgroup.eu
Subject: Re: [HELPER PATCH 1] sysfs: Provide write method for paravirt
Date: Wed, 19 Nov 2025 13:38:24 +0530 [thread overview]
Message-ID: <dadeeb85-779e-44e8-83b7-4c53ad338493@linux.ibm.com> (raw)
In-Reply-To: <2025111922-rearrange-manned-8a47@gregkh>
Hi Greg.
On 11/19/25 1:12 PM, Greg KH wrote:
> On Wed, Nov 19, 2025 at 11:50:59AM +0530, Shrikanth Hegde wrote:
>> This is helper patch which could be used to set the range of CPUs as
>> paravirt. One could make use of this for quick testing of this infra
>> instead of writing arch specific code.
>>
>> This is currently not meant be merged, since paravirt sysfs file is meant
>> to be Read-Only.
>>
>> echo 100-200,600-700 > /sys/devices/system/cpu/paravirt
>> cat /sys/devices/system/cpu/paravirt
>> 100-200,600-700
>>
>> echo > /sys/devices/system/cpu/paravirt
>> cat /sys/devices/system/cpu/paravirt
>>
>> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
>> ---
>> drivers/base/cpu.c | 48 ++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 46 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
>> index 59ceae217b22..043e4f4ce1a9 100644
>> --- a/drivers/base/cpu.c
>> +++ b/drivers/base/cpu.c
>> @@ -375,12 +375,57 @@ static int cpu_uevent(const struct device *dev, struct kobj_uevent_env *env)
>> #endif
>>
>> #ifdef CONFIG_PARAVIRT
>> +static ssize_t store_paravirt_cpus(struct device *dev,
>> + struct device_attribute *attr,
>> + const char *buf, size_t count)
>> +{
>> + cpumask_var_t temp_mask;
>> + int retval = 0;
>> +
>> + if (!alloc_cpumask_var(&temp_mask, GFP_KERNEL))
>> + return -ENOMEM;
>> +
>> + retval = cpulist_parse(buf, temp_mask);
>> + if (retval)
>> + goto free_mask;
>> +
>> + /* ALL cpus can't be marked as paravirt */
>> + if (cpumask_equal(temp_mask, cpu_online_mask)) {
>> + retval = -EINVAL;
>> + goto free_mask;
>> + }
>> + if (cpumask_weight(temp_mask) > num_online_cpus()) {
>> + retval = -EINVAL;
>> + goto free_mask;
>> + }
>> +
>> + /* No more paravirt cpus */
>> + if (cpumask_empty(temp_mask)) {
>> + cpumask_copy((struct cpumask *)&__cpu_paravirt_mask, temp_mask);
>> + } else {
>> + cpumask_copy((struct cpumask *)&__cpu_paravirt_mask, temp_mask);
>> +
>> + /* Enable tick on nohz_full cpu */
>> + int cpu;
>> + for_each_cpu(cpu, temp_mask) {
>> + if (tick_nohz_full_cpu(cpu))
>> + tick_nohz_dep_set_cpu(cpu, TICK_DEP_BIT_SCHED);
>> + }
>> + }
>> +
>> + retval = count;
>> +
>> +free_mask:
>> + free_cpumask_var(temp_mask);
>> + return retval;
>> +}
>> +
>> static ssize_t print_paravirt_cpus(struct device *dev,
>> struct device_attribute *attr, char *buf)
>> {
>> return sysfs_emit(buf, "%*pbl\n", cpumask_pr_args(cpu_paravirt_mask));
>> }
>> -static DEVICE_ATTR(paravirt, 0444, print_paravirt_cpus, NULL);
>> +static DEVICE_ATTR(paravirt, 0644, print_paravirt_cpus, store_paravirt_cpus);
>
> DEVICE_ATTR_RW()?
ok.
>
> And where is the documentation update for this sysfs file change?
>
[RFC PATCH v4 11/17] has the documentation of this sysfs file.
https://lore.kernel.org/all/20251119062100.1112520-12-sshegde@linux.ibm.com/
>> #endif
>>
>> const struct bus_type cpu_subsys = {
>> @@ -675,7 +720,6 @@ static void __init cpu_register_vulnerabilities(void)
>> put_device(dev);
>> }
>> }
>> -
>> #else
>
> Why is this change needed?
>
> thanks,
>
> greg k-h
This is a helper patch. This helps to verify functionality of any combination
of CPUs being marked as paravirt which helped me to test some corner cases.
This is also helpful until the arch specific hint becomes better.
This is also useful for other archs which haven't implemented archs specific handling of
steal time, but want to play around with series for their usecase (ex: S390)
Once arch specific hint becomes better, we could decide to remove it or keep in more appropriate
place. It really is debugfs for infra which says I don't want to use these CPUs for now.
next prev parent reply other threads:[~2025-11-19 8:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 6:20 [RFC PATCH v4 00/17] Paravirt CPUs and push task for less vCPU preemption Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 01/17] sched/docs: Document cpu_paravirt_mask and Paravirt CPU concept Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 02/17] cpumask: Introduce cpu_paravirt_mask Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 03/17] sched/core: Dont allow to use CPU marked as paravirt Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 04/17] sched/debug: Remove unused schedstats Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v5 05/17] sched/fair: Add paravirt movements for proc sched file Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 06/17] sched/fair: Pass current cpu in select_idle_sibling Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 07/17] sched/fair: Don't consider paravirt CPUs for wakeup and load balance Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 08/17] sched/rt: Don't select paravirt CPU for wakeup and push/pull rt task Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 09/17] sched/core: Add support for nohz_full CPUs Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 10/17] sched/core: Push current task from paravirt CPU Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 11/17] sysfs: Add paravirt CPU file Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 12/17] powerpc: method to initialize ec and vp cores Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 13/17] powerpc: enable/disable paravirt CPUs based on steal time Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 14/17] powerpc: process steal values at fixed intervals Shrikanth Hegde
2025-11-19 6:20 ` [RFC PATCH v4 15/17] powerpc: add debugfs file for controlling handling on steal values Shrikanth Hegde
2025-11-19 6:20 ` [HELPER PATCH 1] sysfs: Provide write method for paravirt Shrikanth Hegde
2025-11-19 7:42 ` Greg KH
2025-11-19 8:08 ` Shrikanth Hegde [this message]
2025-11-19 8:20 ` Christophe Leroy
2025-11-19 10:01 ` Shrikanth Hegde
2025-11-19 8:23 ` Greg KH
2025-11-19 9:56 ` Shrikanth Hegde
2025-11-19 6:21 ` [HELPER PATCH 2] helper: disable arch handling if paravirt file being written Shrikanth Hegde
2025-11-19 12:53 ` [RFC PATCH v4 00/17] Paravirt CPUs and push task for less vCPU preemption 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=dadeeb85-779e-44e8-83b7-4c53ad338493@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=huschle@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=srikar@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--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