[Xen-devel] [PATCH]Propagate guest MSR writes to machine MSRs im

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH]Propagate guest MSR writes to machine MSRs immediately
From:	"Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date:	Thu, 21 Jul 2005 17:22:50 +0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Thu, 21 Jul 2005 09:21:50 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcWN1cPauZF2AJonT+mABZg1nLuJsw==
Thread-topic:	[PATCH]Propagate guest MSR writes to machine MSRs immediately

Propagate guest MSR writes to machine MSRs immediately

Right now, we have an exposure between the time the MSR is written
and used by an instruction such as syscall. If there is a context
switch and we do vmx_do_restore_msrs(), everything goes fine. But
if we don't, then we execute the syscall with the wrong MSR.

Signed-off-by: Yunhong Jiang <yunhong.jiang@xxxxxxxxx>
Signed-off-by: Arun Sharma <arun.sharma@xxxxxxxxx>

Thanks
Yunhong Jiang

msr.patch
Description: msr.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] [PATCH]Propagate guest MSR writes to machine MSRs immediatel