| commit | f7d69146549d717ef6cb5a68a3a4452391416f22 | |
| author | Alexander Graf <agraf@suse.de> | |
| Thu, 24 Apr 2014 12:57:04 +0000 (24 14:57 +0200) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Mon, 16 Jun 2014 11:24:41 +0000 (16 13:24 +0200) | ||
| tree | 40e3326e3538a471b175a15f8e5c0d7f25dea89f | treesnapshot (tar.gz zip) |
| parent | 87a91de61a34a7f3222203556df8a67f187360cd | commitdiff |
PPC: spapr: Expose /hypervisor node in device tree
PR KVM supports an ePAPR compliant hypercall interface in parallel to the
normal sPAPR one. Expose the ePAPR /hypervisor node and properties to the
guest so it can use it.
This enables magic page sharing on PR KVM with -M pseries.
However we had a few nasty bugs in the magic page implementation on vcpus
newer than 970 (p7, p8) that KVM now has workarounds for. It indicates that
it does have these workarounds through the PPC_FIXUP_HCALL capability.
To not expose broken guest kernels to issues on host kernels that don't
have the fixups in place, we don't expose working hypercall instructions
when the fixups are not available so that the guest can never active the
magic page.
Signed-off-by: Alexander Graf <agraf@suse.de>
PR KVM supports an ePAPR compliant hypercall interface in parallel to the
normal sPAPR one. Expose the ePAPR /hypervisor node and properties to the
guest so it can use it.
This enables magic page sharing on PR KVM with -M pseries.
However we had a few nasty bugs in the magic page implementation on vcpus
newer than 970 (p7, p8) that KVM now has workarounds for. It indicates that
it does have these workarounds through the PPC_FIXUP_HCALL capability.
To not expose broken guest kernels to issues on host kernels that don't
have the fixups in place, we don't expose working hypercall instructions
when the fixups are not available so that the guest can never active the
magic page.
Signed-off-by: Alexander Graf <agraf@suse.de>
| hw/ppc/spapr.c | diffblobblamehistory |