From: Steffen Eiden <seiden@linux.ibm.com>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Vincent Donnefort <vdonnefort@google.com>,
Quentin Perret <qperret@google.com>,
Sebastian Ene <sebastianene@google.com>,
Hyunwoo Kim <imv4bel@gmail.com>, Fuad Tabba <tabba@google.com>
Subject: Re: [PATCH v6 3/8] KVM: arm64: Factor out reusable vCPU reset helpers
Date: Fri, 17 Jul 2026 14:43:59 +0200 [thread overview]
Message-ID: <20260717124359.319936-B-seiden@linux.ibm.com> (raw)
In-Reply-To: <20260715081238.1891918-4-fuad.tabba@linux.dev>
On Wed, Jul 15, 2026 at 09:12:33AM +0100, Fuad Tabba wrote:
> Pull the reusable pieces out of kvm_reset_vcpu(): expose the reset
> PSTATE values in kvm_arm.h, and split the core register reset and the
> PSCI-driven reset into kvm_reset_vcpu_core() and kvm_reset_vcpu_psci().
> A follow-up series reuses these to reset protected vCPUs at EL2.
>
> No functional change intended.
>
> Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
> Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
That looks good. There is another usecase for this. I did a very similar
thing in [1] to reuse the reset functionality for arm64 on s390. I just
did not the move the code to a different file.
FWIW:
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
[1] https://lore.kernel.org/all/20260706085229.979525-11-seiden@linux.ibm.com/
Steffen
next prev parent reply other threads:[~2026-07-17 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:12 [PATCH v6 0/8] KVM: arm64: pKVM vCPU state management at EL2 Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 1/8] KVM: arm64: Extract MPIDR computation into a shared header Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 2/8] KVM: arm64: Make vcpu_{read,write}_sys_reg available to HYP code Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 3/8] KVM: arm64: Factor out reusable vCPU reset helpers Fuad Tabba
2026-07-17 12:43 ` Steffen Eiden [this message]
2026-07-15 8:12 ` [PATCH v6 4/8] KVM: arm64: Move PSCI helper functions to a shared header Fuad Tabba
2026-07-15 8:24 ` sashiko-bot
2026-07-15 8:28 ` Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 5/8] KVM: arm64: Add host and hypervisor vCPU lookup primitives Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 6/8] KVM: arm64: Minimise EL2's exposure of host VGIC state during world switch Fuad Tabba
2026-07-15 8:37 ` sashiko-bot
2026-07-15 9:18 ` Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 7/8] KVM: arm64: Add primitives to flush/sync the VGIC state at EL2 Fuad Tabba
2026-07-15 8:12 ` [PATCH v6 8/8] KVM: arm64: Implement lazy vCPU state sync for non-protected guests Fuad Tabba
2026-07-15 8:34 ` sashiko-bot
2026-07-15 9:20 ` Fuad Tabba
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=20260717124359.319936-B-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=imv4bel@gmail.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=qperret@google.com \
--cc=sebastianene@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.