Re: [PATCH] KVM: x86: move steal time initialization to vcpu entry time

2015-10-16 Thread Paolo Bonzini
On 15/10/2015 19:10, David Matlack wrote: > > As reported at https://bugs.launchpad.net/qemu/+bug/1494350, > > it is possible to have vcpu->arch.st.last_steal initialized > > from a thread other than vcpu thread, say the iothread, via > > KVM_SET_MSRS. > > > > Which can cause an overflow later

Re: [PATCH] KVM: x86: move steal time initialization to vcpu entry time

2015-10-15 Thread David Matlack
On Wed, Oct 14, 2015 at 3:33 PM, Marcelo Tosatti wrote: > > As reported at https://bugs.launchpad.net/qemu/+bug/1494350, > it is possible to have vcpu->arch.st.last_steal initialized > from a thread other than vcpu thread, say the iothread, via > KVM_SET_MSRS. > > Which can

[PATCH] KVM: x86: move steal time initialization to vcpu entry time

2015-10-14 Thread Marcelo Tosatti
As reported at https://bugs.launchpad.net/qemu/+bug/1494350, it is possible to have vcpu->arch.st.last_steal initialized from a thread other than vcpu thread, say the iothread, via KVM_SET_MSRS. Which can cause an overflow later (when subtracting from vcpu threads sched_info.run_delay). To