From: Robert Hoo <robert.hu@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: robert.hu@intel.com, robert.hu@linux.intel.com,
pbonzini@redhat.com, rth@twiddle.net, thomas.lendacky@amd.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 2/3] x86: Data structure changes to support MSR based features
Date: Thu, 25 Oct 2018 11:06:59 +0800 [thread overview]
Message-ID: <1540436819.80634.2.camel@linux.intel.com> (raw)
In-Reply-To: <20181024101643.GE4096@habkost.net>
On Wed, 2018-10-24 at 07:16 -0300, Eduardo Habkost wrote:
> On Mon, Oct 15, 2018 at 12:47:24PM +0800, Robert Hoo wrote:
> > Add FeatureWordType indicator in struct FeatureWordInfo.
> > Change feature_word_info[] accordingly.
> > Change existing functions that refer to feature_word_info[]
> > accordingly.
> >
> > Signed-off-by: Robert Hoo <robert.hu@linux.intel.com>
> > ---
> > target/i386/cpu.c | 188 +++++++++++++++++++++++++++++++++++++++---
> > ------------
> > 1 file changed, 136 insertions(+), 52 deletions(-)
> >
> > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > index c88876d..d191b9c 100644
> > --- a/target/i386/cpu.c
> > +++ b/target/i386/cpu.c
> > @@ -770,17 +770,36 @@ static void x86_cpu_vendor_words2str(char
> > *dst, uint32_t vendor1,
> > /* missing:
> > CPUID_XSAVE_XSAVEC, CPUID_XSAVE_XSAVES */
> >
> > +typedef enum FeatureWordType {
> > + CPUID_FEATURE_WORD,
> > + MSR_FEATURE_WORD,
> > +} FeatureWordType;
> > +
> > typedef struct FeatureWordInfo {
> > + FeatureWordType type;
> > /* feature flags names are taken from "Intel Processor
> > Identification and
> > * the CPUID Instruction" and AMD's "CPUID Specification".
> > * In cases of disagreement between feature naming
> > conventions,
> > * aliases may be added.
> > */
> > const char *feat_names[32];
> > - uint32_t cpuid_eax; /* Input EAX for CPUID */
> > - bool cpuid_needs_ecx; /* CPUID instruction uses ECX as input
> > */
> > - uint32_t cpuid_ecx; /* Input ECX value for CPUID */
> > - int cpuid_reg; /* output register (R_* constant) */
> > + union {
> > + /* If type==CPUID_FEATURE_WORD */
> > + struct {
> > + uint32_t eax; /* Input EAX for CPUID */
> > + bool needs_ecx; /* CPUID instruction uses ECX as input
> > */
> > + uint32_t ecx; /* Input ECX value for CPUID */
> > + int reg; /* output register (R_* constant) */
> > + } cpuid;
> > + /* If type==MSR_FEATURE_WORD */
> > + struct {
> > + uint32_t index;
> > + struct { /*CPUID that enumerate this MSR*/
> > + FeatureWord cpuid_class;
> > + uint32_t cpuid_flag;
> > + } cpuid_dep;
>
> Aren't you going to use this field anywhere? Probably we want to
> prevent the VM from starting if a bit is set in the feature world
> but the cpuid_dep bit is not set.
>
> e.g.:
> qemu-system-x86_64 -cpu Skylake-Client,-arch-capabilities,+rsba
> probably should fail to start.
How about in x86_cpu_filter_features() filters the MSR feature word, if
its dependent CPUID feature bit is not set?
The filter results will be record in cpu->filtered_features, and print
out, like other filtered features.
>
> > + } msr;
> > + };
>
> [...]
>
next prev parent reply other threads:[~2018-10-25 3:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 4:47 [Qemu-devel] [PATCH v5 0/3] x86: QEMU side support on MSR based features Robert Hoo
2018-10-15 4:47 ` [Qemu-devel] [PATCH v5 1/3] kvm: Add support to KVM_GET_MSR_FEATURE_INDEX_LIST and KVM_GET_MSRS system ioctl Robert Hoo
2018-10-24 9:49 ` Eduardo Habkost
2018-10-15 4:47 ` [Qemu-devel] [PATCH v5 2/3] x86: Data structure changes to support MSR based features Robert Hoo
2018-10-24 9:56 ` Eduardo Habkost
2018-10-24 10:16 ` Eduardo Habkost
2018-10-25 3:06 ` Robert Hoo [this message]
2018-10-25 13:36 ` Eduardo Habkost
2018-10-15 4:47 ` [Qemu-devel] [PATCH v5 3/3] x86: define a new MSR based feature word -- FEATURE_WORDS_ARCH_CAPABILITIES Robert Hoo
2018-10-24 10:06 ` Eduardo Habkost
2018-10-25 3:16 ` Robert Hoo
2018-10-26 3:01 ` Robert Hoo
2018-10-26 8:38 ` Eduardo Habkost
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=1540436819.80634.2.camel@linux.intel.com \
--to=robert.hu@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=rth@twiddle.net \
--cc=thomas.lendacky@amd.com \
/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).