From: Yicong Yang <yangyicong@huawei.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<sudeep.holla@arm.com>, <linux-arm-kernel@lists.infradead.org>
Cc: <dietmar.eggemann@arm.com>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <jonathan.cameron@huawei.com>,
<prime.zeng@hisilicon.com>, <linuxarm@huawei.com>,
<yangyicong@hisilicon.com>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 4/4] arm64: Kconfig: Enable HOTPLUG_SMT
Date: Tue, 14 Nov 2023 12:01:10 +0800 [thread overview]
Message-ID: <20231114040110.54590-5-yangyicong@huawei.com> (raw)
In-Reply-To: <20231114040110.54590-1-yangyicong@huawei.com>
From: Yicong Yang <yangyicong@hisilicon.com>
Enable HOTPLUG_SMT for SMT control.
Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 7b071a00425d..002bcde32575 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -233,6 +233,7 @@ config ARM64
select HAVE_KRETPROBES
select HAVE_GENERIC_VDSO
select HOTPLUG_CORE_SYNC_DEAD if HOTPLUG_CPU
+ select HOTPLUG_SMT if SMP
select IRQ_DOMAIN
select IRQ_FORCED_THREADING
select KASAN_VMALLOC if KASAN
--
2.24.0
next prev parent reply other threads:[~2023-11-14 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 4:01 [PATCH v3 0/4] Support SMT control on arm64 Yicong Yang
2023-11-14 4:01 ` [PATCH v3 1/4] arch_topology: Support basic SMT control for the driver Yicong Yang
2023-11-14 13:42 ` kernel test robot
2023-11-15 15:23 ` kernel test robot
2023-11-20 3:29 ` Yicong Yang
2023-11-14 4:01 ` [PATCH v3 2/4] arch_topology: Support SMT control for OF based system Yicong Yang
2023-11-14 4:01 ` [PATCH v3 3/4] arm64: topology: Support SMT control on ACPI " Yicong Yang
2023-11-14 4:01 ` Yicong Yang [this message]
2023-11-16 4:59 ` [PATCH v3 4/4] arm64: Kconfig: Enable HOTPLUG_SMT kernel test robot
2023-11-20 3:27 ` Yicong Yang
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=20231114040110.54590-5-yangyicong@huawei.com \
--to=yangyicong@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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®