From: wangxiaoming321 <xiaoming.wang@intel.com>
To: tglx@linutronix.de, peterz@infradead.org, linux-kernel@vger.kernel.org
Cc: wangxiaoming321 <xiaoming.wang@intel.com>
Subject: [PATCH] cpu/hotplug: Increase the number of dynamic states
Date: Tue, 19 Dec 2023 11:34:11 +0800 [thread overview]
Message-ID: <20231219033411.816100-1-xiaoming.wang@intel.com> (raw)
In-Reply-To: <20231212025235.775986-1-xiaoming.wang@intel.com>
The dynamically allocatable hotplug state space can be exhausted by
the existing drivers and infrastructure which install CPU hotplug
states dynamically. That prevents new drivers and infrastructure from
installing dynamically allocated states.
Increase the size of the CPUHP_AP_ONLINE_DYN state by 10 to make
room.
Signed-off-by: wangxiaoming321 <xiaoming.wang@intel.com>
---
include/linux/cpuhotplug.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/cpuhotplug.h b/include/linux/cpuhotplug.h
index efc0c0b07efb..c88a58c363f1 100644
--- a/include/linux/cpuhotplug.h
+++ b/include/linux/cpuhotplug.h
@@ -251,7 +251,7 @@ enum cpuhp_state {
CPUHP_AP_RCUTREE_ONLINE,
CPUHP_AP_BASE_CACHEINFO_ONLINE,
CPUHP_AP_ONLINE_DYN,
- CPUHP_AP_ONLINE_DYN_END = CPUHP_AP_ONLINE_DYN + 30,
+ CPUHP_AP_ONLINE_DYN_END = CPUHP_AP_ONLINE_DYN + 40,
/* Must be after CPUHP_AP_ONLINE_DYN for node_states[N_CPU] update */
CPUHP_AP_MM_DEMOTION_ONLINE,
CPUHP_AP_X86_HPET_ONLINE,
--
2.25.1
next prev parent reply other threads:[~2023-12-19 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 2:52 [PATCH] kernel/cpu: The number of CPUHP_AP_ONLINE_DYN (30) is too small that stops the new dynamic states hotplug wangxiaoming321
2023-12-15 19:39 ` Thomas Gleixner
2023-12-19 3:30 ` Wang, Xiaoming
2023-12-19 3:34 ` wangxiaoming321 [this message]
2023-12-20 15:35 ` [tip: smp/core] cpu/hotplug: Increase the number of dynamic states tip-bot2 for xiaoming 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=20231219033411.816100-1-xiaoming.wang@intel.com \
--to=xiaoming.wang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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