commit | 61f4237d5b005767a76f4f3694e68e6f78f392d9 | [log] [tgz] |
---|---|---|
author | Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> | Sat Sep 18 22:25:30 2010 -0700 |
committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | Wed Apr 06 08:31:00 2011 -0400 |
tree | 479a885c9c5000a07db28e1b862931edd6fc537e | |
parent | d88885d0923ae27b01dfcec644f94829b1e46bea [diff] |
xen: just completely disable XSAVE Some (old) versions of Xen just kill the domain if it tries to set any unknown bits in CR4, so we can't reliably probe for OSXSAVE in CR4. Since Xen doesn't support XSAVE for guests at the moment, and no such support is being worked on, there's no downside in just unconditionally masking XSAVE support. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>