cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Zefan Li" <lizefan.x@bytedance.com>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Len Brown" <len.brown@intel.com>, "Pavel Machek" <pavel@ucw.cz>,
	"Shuah Khan" <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kselftest@vger.kernel.org,
	"Frederic Weisbecker" <frederic@kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Valentin Schneider" <vschneid@redhat.com>,
	"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
	"Alex Shi" <alexs@kernel.org>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Michal Koutný" <mkoutny@suse.com>
Subject: Re: [PATCH v2 0/2] cgroup/cpuset: Make cpuset hotplug processing synchronous
Date: Mon, 8 Apr 2024 07:40:33 -1000	[thread overview]
Message-ID: <ZhQsESPi9PwpPhx7@slm.duckdns.org> (raw)
In-Reply-To: <20240404134749.2857852-1-longman@redhat.com>

On Thu, Apr 04, 2024 at 09:47:47AM -0400, Waiman Long wrote:
>  v2:
>   - Found that rebuild_sched_domains() has external callers, revert its
>     change and introduce rebuild_sched_domains_cpuslocked() instead.
> 
> As discussed in the LKML thread [1], the asynchronous nature of cpuset
> hotplug handling code is causing problem with RCU testing. With recent
> changes in the way locking is being handled in the cpuset code, it is
> now possible to make the cpuset hotplug code synchronous again without
> major changes.
> 
> This series enables the hotplug code to call directly into cpuset hotplug
> core without indirection with the exception of the special case of v1
> cpuset becoming empty still being handled indirectly with workqueue.
> 
> A new simple test case was also written to test this special v1 cpuset
> case. The test_cpuset_prs.sh script was also run with LOCKDEP on to
> verify that there is no regression.

Applied to cgroup/for-6.10. Hopefully, this one will work out. Thanks for
working on this.

-- 
tejun

      parent reply	other threads:[~2024-04-08 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 13:47 [PATCH v2 0/2] cgroup/cpuset: Make cpuset hotplug processing synchronous Waiman Long
2024-04-04 13:47 ` [PATCH v2 1/2] " Waiman Long
2024-04-08 15:22   ` Valentin Schneider
2024-04-04 13:47 ` [PATCH v2 2/2] cgroup/cpuset: Add test_cpuset_v1_hp.sh Waiman Long
2024-04-08 17:40 ` Tejun Heo [this message]

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=ZhQsESPi9PwpPhx7@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=alexs@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=cgroups@vger.kernel.org \
    --cc=frederic@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=mkoutny@suse.com \
    --cc=paulmck@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).