diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2018-01-21 17:42:56 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-04-20 17:32:23 +0200 |
commit | 85bd0ba1ff9875798fad94218b627ea9f768f3c3 (patch) | |
tree | 7a1d8741a980a8d8d0a235c1784b2121634a9265 /MAINTAINERS | |
parent | KVM: arm/arm64: vgic: Kick new VCPU on interrupt migration (diff) | |
download | linux-85bd0ba1ff9875798fad94218b627ea9f768f3c3.tar.xz linux-85bd0ba1ff9875798fad94218b627ea9f768f3c3.zip |
arm/arm64: KVM: Add PSCI version selection API
Although we've implemented PSCI 0.1, 0.2 and 1.0, we expose either 0.1
or 1.0 to a guest, defaulting to the latest version of the PSCI
implementation that is compatible with the requested version. This is
no different from doing a firmware upgrade on KVM.
But in order to give a chance to hypothetical badly implemented guests
that would have a fit by discovering something other than PSCI 0.2,
let's provide a new API that allows userspace to pick one particular
version of the API.
This is implemented as a new class of "firmware" registers, where
we expose the PSCI version. This allows the PSCI version to be
save/restored as part of a guest migration, and also set to
any supported version if the guest requires it.
Cc: stable@vger.kernel.org #4.16
Reviewed-by: Christoffer Dall <cdall@kernel.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions