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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2016/3/11 16:53, Liang Chen wrote:
> From: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
> 
> commit 7cae2bedcbd4680b155999655e49c27b9cf020fa upstream
> 
> This patch is needed on lts 3.4, 3.10, 3.12, 3.14, 3.18, and 4.1 for
> the same issue. Can you please to pick it up?
> 

Sure. I'll queue it up for 3.4.y. Thanks!

> 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 avoid that, move steal time accumulation to vcpu entry time,
> before copying steal time data to guest.
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@xxxxxxxxxx>
> Reviewed-by: David Matlack <dmatlack@xxxxxxxxxx>
> Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]