From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KeirFraser <keir@xen.org>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Dugger, Donald D" <donald.d.dugger@intel.com>,
Jan Beulich <JBeulich@suse.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: XSAVE save/restore shortcomings
Date: Fri, 06 Sep 2013 08:04:01 -0700 [thread overview]
Message-ID: <5229EEE1.7050809@linux.intel.com> (raw)
In-Reply-To: <5229EEAC.3050100@redhat.com>
On 09/06/2013 08:03 AM, Paolo Bonzini wrote:
>
> Great, could Intel document the offsets of the MPX save areas too? It's
> somewhat useful to know them in advance, if one wants to read and set
> BNDCFGU and BNDSTATUS.
>
I can push that request to the documentation team.
-hpa
next prev parent reply other threads:[~2013-09-06 15:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 9:55 [PATCH] x86/xsave: fix migration from xsave-capable to xsave-incapable host Jan Beulich
2013-08-30 10:11 ` XSAVE save/restore shortcomings (was: [PATCH] x86/xsave: fix migration from xsave-capable to xsave-incapable host) Jan Beulich
2013-08-30 13:47 ` XSAVE save/restore shortcomings Andrew Cooper
2013-09-05 10:53 ` Paolo Bonzini
2013-09-05 12:01 ` Jan Beulich
2013-09-05 13:58 ` Paolo Bonzini
2013-09-05 14:34 ` Jan Beulich
2013-09-06 3:03 ` Zhang, Yang Z
2013-09-06 6:59 ` Jan Beulich
2013-09-06 7:20 ` Zhang, Yang Z
2013-09-06 7:31 ` Jan Beulich
2013-09-06 7:45 ` Zhang, Yang Z
2013-09-06 11:57 ` Paolo Bonzini
2013-09-06 12:35 ` Jan Beulich
2013-09-06 12:38 ` Paolo Bonzini
2013-09-06 12:39 ` Andrew Cooper
2013-09-06 14:44 ` H. Peter Anvin
2013-09-06 15:03 ` Paolo Bonzini
2013-09-06 15:04 ` H. Peter Anvin [this message]
2013-09-03 5:47 ` [PATCH] x86/xsave: fix migration from xsave-capable to xsave-incapable host Zhang, Yang Z
2013-09-09 11:16 ` Keir Fraser
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=5229EEE1.7050809@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=donald.d.dugger@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.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.