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>,
pauld@redhat.com
Subject: [PATCH v5 0/2] cpuhp: fix some st->target issues
Date: Thu, 17 Nov 2022 11:23:27 -0500 [thread overview]
Message-ID: <20221117162329.3164999-1-pauld@redhat.com> (raw)
Fix a few cpuhp related issues.
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.
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.
v5: Fixed lowercase on first patch title and cleaned up cover letter.
Rebased on v6.1-rc5.
Phil Auld (2):
cpuhp: Make target_store() a nop when target == state
cpuhp: Set cpuhp target for boot cpu
cpu.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.31.1
next reply other threads:[~2022-11-17 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 16:23 Phil Auld [this message]
2022-11-17 16:23 ` [PATCH v5 1/2] cpuhp: Make target_store() a nop when target == state Phil Auld
2022-12-01 11:41 ` [tip: smp/core] " tip-bot2 for Phil Auld
2022-12-02 11:51 ` [tip: smp/core] cpu/hotplug: " tip-bot2 for Phil Auld
2022-11-17 16:23 ` [PATCH v5 2/2] cpuhp: Set cpuhp target for boot cpu Phil Auld
2022-12-01 11:41 ` [tip: smp/core] " tip-bot2 for Phil Auld
2022-12-02 11:50 ` [tip: smp/core] cpu/hotplug: " tip-bot2 for Phil Auld
2022-12-01 12:26 ` [PATCH v5 0/2] cpuhp: fix some st->target issues Phil Auld
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=20221117162329.3164999-1-pauld@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
all inboxes | Powered by JetHome®