From: Sven Schnelle <svens@linux.ibm.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [PATCH 1/2] torture: use for_each_present() loop in torture_online_all()
Date: Thu, 17 Nov 2022 07:30:32 +0100 [thread overview]
Message-ID: <yt9dr0y29jp3.fsf@linux.ibm.com> (raw)
In-Reply-To: <20221115134139.GI4001@paulmck-ThinkPad-P17-Gen-1> (Paul E. McKenney's message of "Tue, 15 Nov 2022 05:41:39 -0800")
Hi Paul,
"Paul E. McKenney" <paulmck@kernel.org> writes:
>> > Yes, rcutorture has lower-level checks for CPUs being hotplugged
>> > behind its back. Which might be sufficient. But this patch is in
>> > response to something bad happening if the CPU is also not present in
>> > the cpu_present_mask. Would that same bad thing happen if rcutorture saw
>> > the CPU in cpu_online_mask, but by the time it attempted to CPU-hotplug
>> > it, that CPU was gone not just from cpu_online_mask, but also from
>> > cpu_present_mask?
>> >
>> > Or are CPUs never removed from cpu_present_mask?
>>
>> In the current implementation CPUs can only be added to the
>> cpu_present_mask, but never removed. This might change in the future
>> when we get support from firmware for that, but the current s390 code
>> doesn't do that.
>
> Very good!
>
> Then could the patch please check that bits are never removed?
> That way the code will complain should firmware support be added.
>
> Thanx, Paul
I'm not sure whether i fully understand that. If the CPU could
be removed from the system and the cpu_present_mask, that could
happen at any time. So i don't see how we should check about that?
Regards
Sven
next prev parent reply other threads:[~2022-11-17 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221111125126.3319474-1-svens@linux.ibm.com>
[not found] ` <20221111125126.3319474-2-svens@linux.ibm.com>
[not found] ` <20221111185331.GA725751@paulmck-ThinkPad-P17-Gen-1>
2022-11-14 15:35 ` [PATCH 1/2] torture: use for_each_present() loop in torture_online_all() Sven Schnelle
2022-11-14 16:30 ` Paul E. McKenney
2022-11-15 6:55 ` Sven Schnelle
2022-11-15 13:41 ` Paul E. McKenney
2022-11-17 6:30 ` Sven Schnelle [this message]
2022-11-17 15:06 ` Paul E. McKenney
2022-11-18 23:23 ` Paul E. McKenney
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=yt9dr0y29jp3.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=dave@stgolabs.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.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