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>, Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: [PATCH] x86/xsave: simplify xcomp_bv initialization
Date: Thu, 17 Dec 2015 17:46:52 +0000 [thread overview]
Message-ID: <5672F50C.3000506@citrix.com> (raw)
In-Reply-To: <5672F7CE02000078000C0D8F@prv-mh.provo.novell.com>
On 17/12/15 16:58, Jan Beulich wrote:
> This eliminates a number of pointless conditionals: Bits 0 and 1 of
> xcomp_bv don't matter anyway, and as long as none of bits 2..62 are
> set, setting bit 63 is pointless too.
xcomp_bv[63] is the indication of whether the area is compressed or not.
It will be set by the processor when an XSAVEC instruction is issued,
and until that point, it doesn't particularly matter as no bits are set.
However, it is an ABI indication of the size of the xsave area. It
turns out that we are redundantly allocating an uncompressed xsave, even
when we will only used the compressed form.
For now, I don't think there is any harm, as the lack of
XSTATE_COMPACTION_ENABLED causes the size indication to actually be
correct, but it will become necessary when we start making use of the
optimisations that compaction allows.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
(On that note, I really should make some patches for my planned cleanup
for XSA-165. I have just been too busy recently.)
next prev parent reply other threads:[~2015-12-17 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 16:58 [PATCH] x86/xsave: simplify xcomp_bv initialization Jan Beulich
2015-12-17 17:46 ` Andrew Cooper [this message]
2015-12-18 10:53 ` Shuai Ruan
[not found] ` <20151218105339.GA24875@shuai.ruan@linux.intel.com>
2015-12-18 11:09 ` 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=5672F50C.3000506@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=shuai.ruan@linux.intel.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.