From: Phil Auld <pauld@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <vschneid@redhat.com>,
Steven Price <steven.price@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [RESEND PATCH v4 0/2] cpuhp: fix some st->target issues
Date: Mon, 3 Oct 2022 10:11:51 -0400 [thread overview]
Message-ID: <Yzrtp9wDUED+72w8@lorien.usersys.redhat.com> (raw)
In-Reply-To: <20220915153751.2123654-1-pauld@redhat.com>
On Thu, Sep 15, 2022 at 11:37:49AM -0400 Phil Auld wrote:
> Fix a couple of cpuhp inconsistencies.
>
> The first prevents target_store() from calling cpu_down() when
> target == state which prevents the cpu being incorrectly marked
> as dying. The second just makes the boot cpu have a valid cpuhp
> target rather than 0 (CPU_OFFLINE) while being in state
> CPU_ONLINE.
>
> A further issue which these two patches don't address is that
> the cpuX/online file looks at the device->offline state and can
> thus get out of sync with the actual cpuhp state if the cpuhp
> target is used to change state.
>
> v3: Added code to make sure st->target == target in the nop case.
>
> v4: Use WARN_ON in the case where state == target but st->target does
> not.
>
> Phil Auld (2):
> cpuhp: make target_store() a nop when target == state
> cpuhp: Set cpuhp target for boot cpu
>
> kernel/cpu.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> --
> 2.31.1
>
Pingy McPing-face :)
Peter? Anyone? It's really not ideal to have a cpu marked dying when
it isn't actually going down. Please take a look.
Thanks for your time.
Cheers,
Phil
--
prev parent reply other threads:[~2022-10-03 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 15:37 [RESEND PATCH v4 0/2] cpuhp: fix some st->target issues Phil Auld
2022-09-15 15:37 ` [RESEND PATCH v4 1/2] cpuhp: make target_store() a nop when target == state Phil Auld
2022-09-15 15:37 ` [RESEND PATCH v4 2/2] cpuhp: Set cpuhp target for boot cpu Phil Auld
2022-10-03 14:11 ` Phil Auld [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=Yzrtp9wDUED+72w8@lorien.usersys.redhat.com \
--to=pauld@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=steven.price@arm.com \
--cc=tglx@linutronix.de \
--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