From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>,
Harmandeep Kaur <write.harmandeep@gmail.com>,
Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: [PATCH 1/4] x86/xstate: fix xcomp_bv initialization
Date: Fri, 29 Jan 2016 15:07:16 +0000 [thread overview]
Message-ID: <56AB8024.9040607@citrix.com> (raw)
In-Reply-To: <56AB4C7902000078000CC53B@prv-mh.provo.novell.com>
On 29/01/16 10:26, Jan Beulich wrote:
> We must not clear the compaction bit when using XSAVES/XRSTORS. And
> we need to guarantee that xcomp_bv never has any bits clear which
> are set in xstate_bv (which requires partly undoing commit 83ae0bb226
> ["x86/xsave: simplify xcomp_bv initialization"]). Split initialization
> of xcomp_bv from the other FPU/SSE/AVX related state setup in
> arch_set_info_guest() and hvm_load_cpu_ctxt().
>
> Reported-by: Harmandeep Kaur <write.harmandeep@gmail.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2016-01-29 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 10:22 [PATCH 0/4] x86: xsave{c,s} fixes and adjustments Jan Beulich
2016-01-29 10:26 ` [PATCH 1/4] x86/xstate: fix xcomp_bv initialization Jan Beulich
2016-01-29 15:07 ` Andrew Cooper [this message]
2016-01-29 10:27 ` [PATCH 2/4] x86: adjust xsave structure attributes Jan Beulich
2016-01-29 15:07 ` Andrew Cooper
2016-01-29 10:29 ` [PATCH 3/4] x86/xstate: fix fault behavior on XRSTORS Jan Beulich
2016-01-29 16:48 ` Andrew Cooper
2016-01-29 17:00 ` Jan Beulich
2016-02-01 9:13 ` [PATCH v2 " Jan Beulich
2016-02-01 11:22 ` Andrew Cooper
2016-01-29 10:30 ` [PATCH 4/4] x86/xstate: extend validation to cover full header Jan Beulich
2016-01-29 16:55 ` Andrew Cooper
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=56AB8024.9040607@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=shuai.ruan@linux.intel.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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.