From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, maz@kernel.org, will@kernel.org,
oupton@kernel.org, aneesh.kumar@kernel.org, steven.price@arm.com,
linux-kernel@vger.kernel.org, alexandru.elisei@arm.com,
tabba@google.com, Oliver Upton <oliver.upton@linux.dev>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [kvmtool PATCH v5 06/15] arm64: Use KVM_SET_MP_STATE ioctl to power off non-boot vCPUs
Date: Thu, 8 Jan 2026 17:57:44 +0000 [thread overview]
Message-ID: <20260108175753.1292097-7-suzuki.poulose@arm.com> (raw)
In-Reply-To: <20260108175753.1292097-1-suzuki.poulose@arm.com>
From: Oliver Upton <oliver.upton@linux.dev>
Using the POWER_OFF flag in kvm_vcpu_init gets in the way of resetting a
vCPU in response to a PSCI CPU_ON call, for obvious reasons. Drop the
flag in favor of using the KVM_SET_MP_STATE call for non-boot vCPUs.
Reviewed-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
---
arm64/kvm-cpu.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/arm64/kvm-cpu.c b/arm64/kvm-cpu.c
index 3d914112..c7286484 100644
--- a/arm64/kvm-cpu.c
+++ b/arm64/kvm-cpu.c
@@ -143,10 +143,6 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm *kvm, unsigned long cpu_id)
if (vcpu->kvm_run == MAP_FAILED)
die("unable to mmap vcpu fd");
- /* VCPU 0 is the boot CPU, the others start in a poweroff state. */
- if (cpu_id > 0)
- vcpu_init.features[0] |= (1UL << KVM_ARM_VCPU_POWER_OFF);
-
/* Set KVM_ARM_VCPU_PSCI_0_2 if available */
if (kvm__supports_extension(kvm, KVM_CAP_ARM_PSCI_0_2)) {
vcpu_init.features[0] |= (1UL << KVM_ARM_VCPU_PSCI_0_2);
@@ -201,6 +197,16 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm *kvm, unsigned long cpu_id)
if (err || target->init(vcpu))
die("Unable to initialise vcpu");
+ /* VCPU 0 is the boot CPU, the others start in a poweroff state. */
+ if (cpu_id > 0) {
+ struct kvm_mp_state mp_state = {
+ .mp_state = KVM_MP_STATE_STOPPED,
+ };
+
+ if (ioctl(vcpu->vcpu_fd, KVM_SET_MP_STATE, &mp_state))
+ die_perror("KVM_SET_MP_STATE failed");
+ }
+
coalesced_offset = ioctl(kvm->sys_fd, KVM_CHECK_EXTENSION,
KVM_CAP_COALESCED_MMIO);
if (coalesced_offset)
--
2.43.0
next prev parent reply other threads:[~2026-01-08 17:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 17:57 [kvmtool PATCH v5 00/15] arm64: Handle PSCI calls in userspace Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 01/15] Allow pausing the VM from vcpu thread Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 02/15] update_headers: arm64: Track psci.h for PSCI definitions Suzuki K Poulose
2026-02-09 15:51 ` Will Deacon
2026-02-27 10:23 ` Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 03/15] update headers: Linux v6.18 Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 04/15] Import arm-smccc.h from " Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 05/15] arm64: Stash kvm_vcpu_init for later use Suzuki K Poulose
2026-01-08 17:57 ` Suzuki K Poulose [this message]
2026-01-08 17:57 ` [kvmtool PATCH v5 07/15] arm64: Expose ARM64_CORE_REG() for general use Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 08/15] arm64: Add support for finding vCPU for given MPIDR Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 09/15] arm64: Add skeleton implementation for PSCI Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 10/15] arm64: psci: Implement CPU_SUSPEND Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 11/15] arm64: psci: Implement CPU_ON Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 12/15] arm64: psci: Implement AFFINITY_INFO Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 13/15] arm64: psci: Implement MIGRATE_INFO_TYPE Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 14/15] arm64: psci: Implement SYSTEM_{OFF,RESET} Suzuki K Poulose
2026-01-08 17:57 ` [kvmtool PATCH v5 15/15] arm64: smccc: Start sending PSCI to userspace Suzuki K Poulose
2026-02-09 16:25 ` [kvmtool PATCH v5 00/15] arm64: Handle PSCI calls in userspace Will Deacon
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=20260108175753.1292097-7-suzuki.poulose@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=oupton@kernel.org \
--cc=steven.price@arm.com \
--cc=tabba@google.com \
--cc=will@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
all inboxes | Powered by JetHome®