From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: weidong.han@intel.com, xen-devel@lists.xensource.com,
JBeulich@novell.com, Tim.Deegan@citrix.com
Subject: xsave=0 workaround needed on 3.2 kernels with Xen 4.1 or Xen-unstable.
Date: Mon, 30 Apr 2012 15:37:13 -0400 [thread overview]
Message-ID: <20120430193713.GA12817@phenom.dumpdata.com> (raw)
I somehow thought that this has been fixed but I've been
getting reports that people are running into this.
What kind of fix do I need the in the kernel? I see this:
255 xen_cpuid(&ax, &bx, &cx, &dx);
256
257 xsave_mask =
258 (1 << (X86_FEATURE_XSAVE % 32)) |
259 (1 << (X86_FEATURE_OSXSAVE % 32));
260
261 /* Xen will set CR4.OSXSAVE if supported and not disabled by force */
262 if ((cx & xsave_mask) != xsave_mask)
263 cpuid_leaf1_ecx_mask &= ~xsave_mask; /* disable XSAVE & OSXSAVE */
264 }
But do I need some other one?
next reply other threads:[~2012-04-30 19:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 19:37 Konrad Rzeszutek Wilk [this message]
2012-05-02 9:00 ` xsave=0 workaround needed on 3.2 kernels with Xen 4.1 or Xen-unstable Jan Beulich
2012-05-02 18:42 ` AP
2012-05-03 9:15 ` Jan Beulich
2012-05-03 18:09 ` AP
2012-05-04 19:30 ` AP
2012-05-07 7:15 ` Jan Beulich
2012-05-07 16:07 ` Konrad Rzeszutek Wilk
2012-05-07 22:55 ` Jeremy Fitzhardinge
2012-05-07 23:57 ` AP
2012-05-08 0:08 ` Konrad Rzeszutek Wilk
2012-05-08 0:41 ` AP
2012-05-08 16:39 ` Konrad Rzeszutek Wilk
2012-05-08 17:02 ` Matt Wilson
2012-05-09 0:35 ` Konrad Rzeszutek Wilk
2012-05-09 13:11 ` Konrad Rzeszutek Wilk
2012-05-09 13:30 ` Ian Campbell
2012-05-09 13:34 ` Jan Beulich
2012-05-09 17:38 ` Konrad Rzeszutek Wilk
2012-05-10 19:39 ` Jeff Law
2012-05-10 20:57 ` Konrad Rzeszutek Wilk
2012-05-11 0:58 ` Konrad Rzeszutek Wilk
2012-05-11 2:27 ` Jeff Law
2012-05-11 8:23 ` Jan Beulich
2012-05-10 20:15 ` Jeff Law
2012-05-08 6:25 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120430193713.GA12817@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=Tim.Deegan@citrix.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.