aboutsummaryrefslogtreecommitdiffstats
path: root/tools/arch
diff options
context:
space:
mode:
authorRavi Bangoria <ravi.bangoria@linux.ibm.com>2020-12-16 16:12:16 +0530
committerPaul Mackerras <paulus@ozlabs.org>2021-02-10 14:31:08 +1100
commitafe75049303f75c73a97d635a4d353c7d571d1a3 (patch)
tree998919096486724bdfe051fccd955e262cf0282f /tools/arch
parentDocumentation: kvm: fix warning (diff)
downloadlinux-dev-afe75049303f75c73a97d635a4d353c7d571d1a3.tar.xz
linux-dev-afe75049303f75c73a97d635a4d353c7d571d1a3.zip
KVM: PPC: Book3S HV: Allow nested guest creation when L0 hv_guest_state > L1
On powerpc, L1 hypervisor takes help of L0 using H_ENTER_NESTED hcall to load L2 guest state in cpu. L1 hypervisor prepares the L2 state in struct hv_guest_state and passes a pointer to it via hcall. Using that pointer, L0 reads/writes that state directly from/to L1 memory. Thus L0 must be aware of hv_guest_state layout of L1. Currently it uses version field to achieve this. i.e. If L0 hv_guest_state.version != L1 hv_guest_state.version, L0 won't allow nested kvm guest. This restriction can be loosened up a bit. L0 can be taught to understand older layout of hv_guest_state, if we restrict the new members to be added only at the end, i.e. we can allow nested guest even when L0 hv_guest_state.version > L1 hv_guest_state.version. Though, the other way around is not possible. Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com> Reviewed-by: Fabiano Rosas <farosas@linux.ibm.com> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'tools/arch')
0 files changed, 0 insertions, 0 deletions