diff options
| author | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2005-07-21 13:59:08 +0000 |
|---|---|---|
| committer | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2005-07-21 13:59:08 +0000 |
| commit | 88490a29fe5aae0bf60864afd3807e5e8a67f88f (patch) | |
| tree | 0bde50b98c262a196f4555dba0a03a991c354ba3 /tools/python/xen/sv/RestoreDomain.py | |
| parent | a63fbe2fb406996cc52226cfbc667564fecfb00d (diff) | |
| download | xen-88490a29fe5aae0bf60864afd3807e5e8a67f88f.tar.gz xen-88490a29fe5aae0bf60864afd3807e5e8a67f88f.tar.bz2 xen-88490a29fe5aae0bf60864afd3807e5e8a67f88f.zip | |
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@intel.com>
Signed-off-by: Arun Sharma <arun.sharma@intel.com>
Diffstat (limited to 'tools/python/xen/sv/RestoreDomain.py')
0 files changed, 0 insertions, 0 deletions