From: Frederic Weisbecker <frederic@kernel.org>
To: Peng Wang <peng_wang@linux.alibaba.com>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
Waiman Long <longman@redhat.com>, Tejun Heo <tj@kernel.org>,
He Rongguang <herongguang@linux.alibaba.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
driver-core@lists.linux.dev, linux-trace-kernel@vger.kernel.org,
cgroups@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/2] tick/nohz: Add a policy dependency for full dynticks
Date: Thu, 29 Oct 2026 17:49:10 +0100 [thread overview]
Message-ID: <auN5Bku9w2VDZFFX@localhost.localdomain> (raw)
In-Reply-To: <auNuLZiBZyHLFYUr@MacBook-Pro.local>
Le Fri, Oct 30, 2026 at 12:02:53AM +0800, Peng Wang a écrit :
> > Ok in that case, do you know about the current work in progress
> > to make nohz_full opt-able through cpusets? It implies taking the
> > target CPUs offline shortly but the policy is to be setup before VM
> > is launched, right?
>
> Not always. Waiman mentioned the cpuset work earlier; it could
> cover selecting the policy before a new VM starts.
>
> Some customers express a preference for host tick suppression
> through the management interface when changing workloads within
> a running VM. The host operator decides whether to allow
> suppression on the CPUs backing that VM.
I think people should know ahead if they will run latency critical workloads
or common workloads in their VMs. Because those are completely different.
>
> We want to support revisiting that decision while keeping those
> CPUs online and the VM running, with nohz_full membership
> unchanged. Could such an operation fit into the cpuset work?
If that is really necessary then I guess we can have a file to control that
in cpuset once the nohz_full interface is ready. Though I'm a bit skeptical due
to the overhead of user <-> kernel transitions and housekeeping.
Thanks.
>
> Thanks,
> Peng
>
> >
> > Thanks.
> >
> > --
> > Frederic Weisbecker
> > SUSE Labs
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-10-29 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 13:13 [RFC PATCH v2 0/2] tick/nohz: Add per-CPU control of non-idle tick suppression Peng Wang
2026-10-17 13:13 ` [RFC PATCH v2 1/2] tick/nohz: Add a policy dependency for full dynticks Peng Wang
2026-10-23 15:00 ` Frederic Weisbecker
2026-10-23 16:32 ` Peng Wang
2026-10-28 15:58 ` Frederic Weisbecker
2026-10-29 6:41 ` Peng Wang
2026-10-29 14:02 ` Frederic Weisbecker
2026-10-29 16:02 ` Peng Wang
2026-10-29 16:49 ` Frederic Weisbecker [this message]
2026-10-17 13:13 ` [RFC PATCH v2 2/2] cpu: Add per-CPU control of non-idle tick suppression Peng Wang
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=auN5Bku9w2VDZFFX@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=cgroups@vger.kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=herongguang@linux.alibaba.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peng_wang@linux.alibaba.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
--cc=tj@kernel.org \
/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