summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorMarc Zyngier <marc.zyngier@arm.com>2018-01-21 19:42:56 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-05-01 22:58:27 +0300
commite5a290c4ff77c9fb3fcb1dee7cfb356969daeee2 (patch)
treee61d3d273424c6dc024b029f333fa9c3f966ee94 /tools
parenta2066aa76a7a487b93bc6135b6add2f0036d4ef6 (diff)
downloadlinux-e5a290c4ff77c9fb3fcb1dee7cfb356969daeee2.tar.xz
arm/arm64: KVM: Add PSCI version selection API
commit 85bd0ba1ff9875798fad94218b627ea9f768f3c3 upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions