mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
	<xen-devel@lists.xenproject.org>
Cc: <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH v3 09/11] x86/xen: use capabilities instead of fake cpuid values for xsave
Date: Tue, 18 Apr 2017 11:02:03 +0100	[thread overview]
Message-ID: <2df54917-e8d1-403a-20ff-b956e568bce8@citrix.com> (raw)
In-Reply-To: <20170418063119.11654-10-jgross@suse.com>

On 18/04/17 07:31, Juergen Gross wrote:
> @@ -281,22 +274,24 @@ static bool __init xen_check_mwait(void)
>  	return false;
>  #endif
>  }
> -static void __init xen_init_cpuid_mask(void)
> +
> +static bool __init xen_check_xsave(void)
>  {
> -	unsigned int ax, bx, cx, dx;
> -	unsigned int xsave_mask;
> +	unsigned int err, eax, edx;
>  
> -	ax = 1;
> -	cx = 0;
> -	cpuid(1, &ax, &bx, &cx, &dx);
> +	/* Test OSXSAVE capability via xgetbv instruction. */

The code is fine, but this comment isn't going to be any help to people
reading this code in 6 months time.

How about this:

"Xen 4.0 and older accidentally leaked the host XSAVE flag into guest
view, despite not being able to support guests using the functionality. 
Probe for the actual availability of XSAVE by seeing whether xgetbv
executes successfully or raises #UD."

Everything else is fine, so Reviewed-by: Andrew Cooper
<andrew.cooper3@citrix.com>

~Andrew

  reply	other threads:[~2017-04-18 10:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  6:31 [PATCH v3 00/11] x86: xen cpuid() cleanup Juergen Gross
2017-04-18  6:31 ` [PATCH v3 01/11] xen: set cpu capabilities from xen_start_kernel() Juergen Gross
2017-04-18  6:31 ` [PATCH v3 02/11] x86/xen: don't indicate DCA support in pv domains Juergen Gross
2017-04-18  6:31 ` [PATCH v3 03/11] x86/xen: use capabilities instead of fake cpuid values for aperf Juergen Gross
2017-04-18  6:31 ` [PATCH v3 04/11] x86/xen: use capabilities instead of fake cpuid values for mtrr Juergen Gross
2017-04-18  6:31 ` [PATCH v3 05/11] x86/xen: use capabilities instead of fake cpuid values for acc Juergen Gross
2017-04-18  6:31 ` [PATCH v3 06/11] x86/xen: use capabilities instead of fake cpuid values for acpi Juergen Gross
2017-04-18  6:31 ` [PATCH v3 07/11] x86/xen: use capabilities instead of fake cpuid values for mwait Juergen Gross
2017-04-18  6:31 ` [PATCH v3 08/11] x86/xen: use capabilities instead of fake cpuid values for x2apic Juergen Gross
2017-04-18  6:31 ` [PATCH v3 09/11] x86/xen: use capabilities instead of fake cpuid values for xsave Juergen Gross
2017-04-18 10:02   ` Andrew Cooper [this message]
2017-04-18 11:56     ` [Xen-devel] " Juergen Gross
2017-04-21 14:24   ` Boris Ostrovsky
2017-04-21 14:38     ` Juergen Gross
2017-04-21 14:45       ` Andrew Cooper
2017-04-21 14:51         ` Boris Ostrovsky
2017-04-24  6:23           ` Juergen Gross
2017-04-18  6:31 ` [PATCH v3 10/11] vmware: set cpu capabilities during platform initialization Juergen Gross
2017-04-18  6:31 ` [PATCH v3 11/11] x86/cpu: remove hypervisor specific set_cpu_features Juergen Gross

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=2df54917-e8d1-403a-20ff-b956e568bce8@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome