From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 6/6] x86/cpuid: Only recalculate the shared feature bits once
Date: Thu, 19 Jan 2017 11:01:47 +0000 [thread overview]
Message-ID: <20170119110147.GH5089@citrix.com> (raw)
In-Reply-To: <1484768458-13117-7-git-send-email-andrew.cooper3@citrix.com>
On Wed, Jan 18, 2017 at 07:40:58PM +0000, Andrew Cooper wrote:
> With accurate vendor information available, the shared bits can be sorted out
> during recalculation, rather than at query time in the legacy cpuid path.
>
> This means that:
> * Duplication can be dropped from the automatically generated cpuid data.
> * The toolstack need not worry about setting them appropriately.
> * They can be dropped from the system maximum featuresets.
>
> While editing gen-cpuid.py, reflow some comments which exceeded the expected
> line length.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> CC: Wei Liu <wei.liu2@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-19 11:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 19:40 [PATCH 0/6] x86/cpuid: Handling of simple leaves in guest_cpuid() Andrew Cooper
2017-01-18 19:40 ` [PATCH 1/6] x86/cpuid: Hide VT-x/SVM from HVM-based control domains Andrew Cooper
2017-01-19 3:56 ` Doug Goldstein
2017-01-19 14:13 ` Andrew Cooper
2017-01-20 15:44 ` Jan Beulich
2017-01-24 14:38 ` Roger Pau Monné
2017-01-24 15:10 ` Jan Beulich
2017-01-24 15:41 ` Roger Pau Monné
2017-01-24 16:17 ` Andrew Cooper
2017-01-18 19:40 ` [PATCH 2/6] x86/cpuid: Remove BUG_ON() condition from guest_cpuid() Andrew Cooper
2017-01-19 3:57 ` Doug Goldstein
2017-01-20 15:45 ` Jan Beulich
2017-01-18 19:40 ` [PATCH 3/6] x86/cpuid: Handle leaf 0 in guest_cpuid() Andrew Cooper
2017-01-19 4:02 ` Doug Goldstein
2017-01-20 15:48 ` Jan Beulich
2017-01-18 19:40 ` [PATCH 4/6] x86/cpuid: Handle leaf 0x80000000 " Andrew Cooper
2017-01-19 4:03 ` Doug Goldstein
2017-01-20 15:58 ` Jan Beulich
2017-01-20 16:02 ` Andrew Cooper
2017-01-18 19:40 ` [PATCH 5/6] x86/cpuid: Handle the long vendor string " Andrew Cooper
2017-01-19 4:03 ` Doug Goldstein
2017-01-20 16:00 ` Jan Beulich
2017-01-20 16:03 ` Andrew Cooper
2017-01-18 19:40 ` [PATCH 6/6] x86/cpuid: Only recalculate the shared feature bits once Andrew Cooper
2017-01-19 4:03 ` Doug Goldstein
2017-01-19 11:01 ` Wei Liu [this message]
2017-01-20 16:06 ` 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=20170119110147.GH5089@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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.