> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
> Sent: Thursday, May 2, 2019 7:52 AM
> 
> 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.
> 
> Refresh shadow_gs value when the context being saved is for the current
> vCPU.
> 
> Signed-off-by: Tamas K Lengyel <ta...@tklengyel.com>

Acked-by: Kevin Tian <kevin.t...@intel.com>

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

Reply via email to