On 01/05/2019 08:17, Razvan Cojocaru wrote:
> On 5/1/19 7:22 AM, Tamas K Lengyel wrote:
>> Currently the gs_shadow value is only cached when the vCPU is being scheduled
>> out by Xen. Reporting this (usually) stale value through vm_event is 
>> incorrect,
>> since it doesn't represent the actual state of the vCPU at the time the event
>> was recorded. This prevents vm_event subscribers from correctly finding 
>> kernel
>> structures in the guest when it is trapped while in ring3.
> Isn't the VCPU always scheduled out (since it is paused) with sync
> vm_events? Is this an async fix only?

Paused isn't always scheduled out.  It can be half-idle with state still
in hardware.

>
> In any case,
>
> Acked-by: Razvan Cojocaru <rcojoc...@bitdefender.com>

Reviewed-by: Andrew Cooper <andrew.coop...@citrix.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to