From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Huaitong Han <huaitong.han@intel.com>, jbeulich@suse.com, keir@xen.org
Cc: shuai.ruan@linux.intel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH V2] x86/xsaves: get_xsave_addr, check xsave header and support uncompressed format
Date: Fri, 18 Dec 2015 15:13:09 +0000 [thread overview]
Message-ID: <56742285.9040503@citrix.com> (raw)
In-Reply-To: <1450450983-6095-1-git-send-email-huaitong.han@intel.com>
On 18/12/15 15:03, Huaitong Han wrote:
> The check needs to be against the xsave header in the area, rather than Xen's
> maximum xfeature_mask. A guest might easily have a smaller xcr0 than the
> maximum Xen is willing to allow, causing the pointer below to be bogus.
>
> The get_xsave_addr() is modified to support uncompressed xstate areas.
>
> Signed-off-by: Huaitong Han <huaitong.han@intel.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
prev parent reply other threads:[~2015-12-18 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 15:03 [PATCH V2] x86/xsaves: get_xsave_addr, check xsave header and support uncompressed format Huaitong Han
2015-12-18 15:13 ` Andrew Cooper [this message]
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=56742285.9040503@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=huaitong.han@intel.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=shuai.ruan@linux.intel.com \
--cc=xen-devel@lists.xen.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.