aboutsummaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2014-08-14 15:39:33 -0600
committerPaolo Bonzini <pbonzini@redhat.com>2014-08-25 18:53:42 +0200
commitd1ae67f626c5ed5729e1d8212834291b409d26df (patch)
treeb7a7d9199f70689d7542664d81c78470819cc783 /HACKING
parentd8b5c67b05420d966664664ff287af05b884bdd1 (diff)
downloadqemu-d1ae67f626c5ed5729e1d8212834291b409d26df.zip
qemu-d1ae67f626c5ed5729e1d8212834291b409d26df.tar.gz
qemu-d1ae67f626c5ed5729e1d8212834291b409d26df.tar.bz2
x86: kvm: Add MTRR support for kvm_get|put_msrs()
The MTRR state in KVM currently runs completely independent of the QEMU state in CPUX86State.mtrr_*. This means that on migration, the target loses MTRR state from the source. Generally that's ok though because KVM ignores it and maps everything as write-back anyway. The exception to this rule is when we have an assigned device and an IOMMU that doesn't promote NoSnoop transactions from that device to be cache coherent. In that case KVM trusts the guest mapping of memory as configured in the MTRR. This patch updates kvm_get|put_msrs() so that we retrieve the actual vCPU MTRR settings and therefore keep CPUX86State synchronized for migration. kvm_put_msrs() is also used on vCPU reset and therefore allows future modificaitons of MTRR state at reset to be realized. Note that the entries array used by both functions was already slightly undersized for holding every possible MSR, so this patch increases it beyond the 28 new entries necessary for MTRR state. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com> Cc: qemu-stable@nongnu.org Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'HACKING')
0 files changed, 0 insertions, 0 deletions