https://bugzilla.kernel.org/show_bug.cgi?id=61971
--- Comment #16 from Paolo Bonzini ---
Yes, that's expected. You also need the patch I send on Thursday, that you
were CCed on (KVM: x86: fix KVM_SET_XCRS for CPUs that do not support XSAVE).
--
You are receiving this mail because:
You are watc
https://bugzilla.kernel.org/show_bug.cgi?id=61971
--- Comment #15 from Magnus Boden ---
I have no upgraded all three hosts with the kernel from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git
Using the branch next, last commit on that tree was:
commit d570142674890fe10b3d7d86aa105e3dfce1ddfa
Merge
On KVM, the KVM_SET_XSAVE would be executed with a 0 xstate_bv,
and not restore anything.
Since FP and SSE data are always valid, set them in xstate_bv at reset
time. In fact, that value is the same that KVM_GET_XSAVE returns on
pre-XSAVE hosts.
Signed-off-by: Paolo Bonzini
Signed-off-by: Gleb
The data in leaf 0Dh depends on information from other feature bits.
Instead of passing it blindly from the host, compute it based on
whether these feature bits are enabled.
Signed-off-by: Paolo Bonzini
Signed-off-by: Gleb Natapov
---
target-i386/cpu.c | 65 +
Anthony,
The following changes since commit a684f3cf9b9b9c3cb82be87aafc463de8974610c:
Merge remote-tracking branch 'kraxel/seabios-1.7.3.2' into staging
(2013-09-30 17:15:27 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
for yo
From: Jan Kiszka
rom_state_paddr is guest provided (caller address of outw(VAPIC_PORT) +
writen 16-bit value) and can be influenced to point beyond the end of
the host memory backing the guest's RAM. Make sure we do not use this
pointer to actually read beyond the limits.
Reading arbitrary guest
2013-10-17 12:39+0200, Paolo Bonzini:
> Il 17/10/2013 12:10, Radim Krčmář ha scritto:
> > Simple replacement where possible.
> > Saves us problematic access to the structure and allows optimalizations
> > and bug fixes to take place.
>
> I think you should introduce this first as a simple wrapper
