All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH] x86/HVM: hide features dependent on XSAVE when booted with "no-xsave"
Date: Fri, 27 Nov 2015 16:00:36 +0000	[thread overview]
Message-ID: <56587E24.4050209@citrix.com> (raw)
In-Reply-To: <5658478B02000078000B9A3E@prv-mh.provo.novell.com>

On 27/11/15 11:07, Jan Beulich wrote:
> ... or when the guest has the XSAVE feature hidden by CPUID policy.
> Not doing so is at best confusing to guests.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> One question is whether we shouldn't switch leaf 7 to white listing,
> just like done for PV guests.

The general comments from my PV side review apply here as well.

My levelling series has also moved all cpuid information to
whitelist-based.  It is the only safe way of doing things.

I chose to defer AVX512 work from my levelling series, because it is
rather more complicated than this, and there was insufficient details in
the Extention reference.  In particular, there is an suggestion that one
of the feature bits indicates support for non-EVEX encoded instructions
with k$N opmasks, which is not dependent on AVX512F.

It is also odd to see it added to HVM guests but not PV.  I would be
tempted to leave all the AVX512 bits until the groundwork from my series
is in.  It is destined for Skylake-EP which is still a year off.

~Andrew

  reply	other threads:[~2015-11-27 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 11:07 [PATCH] x86/HVM: hide features dependent on XSAVE when booted with "no-xsave" Jan Beulich
2015-11-27 16:00 ` Andrew Cooper [this message]
2015-11-27 17:10   ` Jan Beulich
2015-11-27 17:18     ` 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=56587E24.4050209@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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.