From: Huaitong Han <huaitong.han@intel.com>
To: jbeulich@suse.com, andrew.cooper3@citrix.com, keir@xen.org
Cc: Huaitong Han <huaitong.han@intel.com>,
shuai.ruan@linux.intel.com, xen-devel@lists.xen.org
Subject: [PATCH V2] x86/xsaves: get_xsave_addr, check xsave header and support uncompressed format
Date: Fri, 18 Dec 2015 23:03:03 +0800 [thread overview]
Message-ID: <1450450983-6095-1-git-send-email-huaitong.han@intel.com> (raw)
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>
---
xen/arch/x86/xstate.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/xen/arch/x86/xstate.c b/xen/arch/x86/xstate.c
index b65da38..4e87ab3 100644
--- a/xen/arch/x86/xstate.c
+++ b/xen/arch/x86/xstate.c
@@ -146,12 +146,15 @@ static void __init setup_xstate_comp(void)
}
}
-static void *get_xsave_addr(void *xsave, unsigned int xfeature_idx)
+static void *get_xsave_addr(struct xsave_struct *xsave,
+ unsigned int xfeature_idx)
{
- if ( !((1ul << xfeature_idx) & xfeature_mask) )
+ if ( !((1ul << xfeature_idx) & xsave->xsave_hdr.xstate_bv) )
return NULL;
- return xsave + xstate_comp_offsets[xfeature_idx];
+ return (void *)xsave + (xsave_area_compressed(xsave)
+ ? xstate_comp_offsets
+ : xstate_offsets)[xfeature_idx];
}
void expand_xsave_states(struct vcpu *v, void *dest, unsigned int size)
--
2.4.3
next reply other threads:[~2015-12-18 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 15:03 Huaitong Han [this message]
2015-12-18 15:13 ` [PATCH V2] x86/xsaves: get_xsave_addr, check xsave header and support uncompressed format 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=1450450983-6095-1-git-send-email-huaitong.han@intel.com \
--to=huaitong.han@intel.com \
--cc=andrew.cooper3@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).