From: Sergey Dyasli <sergey.dyasli@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
Kevin Tian <kevin.tian@intel.com>,
"jun.nakajima@intel.com" <jun.nakajima@intel.com>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: [PATCH v5 1/5] x86/msr: add VMX MSRs definitions and populate Raw domain policy
Date: Thu, 22 Mar 2018 09:39:36 +0000 [thread overview]
Message-ID: <1521711576.3556.2.camel@citrix.com> (raw)
In-Reply-To: <b643a58a-fb03-eefb-42c6-b6d879099845@citrix.com>
On Wed, 2018-03-21 at 19:52 +0000, Andrew Cooper wrote:
> On 28/02/18 16:09, Sergey Dyasli wrote:
> >
> > + struct {
> > + /* 0x00000480 MSR_IA32_VMX_BASIC */
> > + union {
> > + uint64_t raw;
> > + struct {
> > + uint32_t vmcs_revision_id:31;
>
> vmcs_rev_id
>
> > + bool mbz:1; /* 31 always zero */
>
> Is this really mbz? Isn't this the shadow identifier bit for shadow vmcs's?
Yes, in vmcs itself it's the shadow bit. However, it is always zero in
MSR since the job of MSR is to report vmcs revision identifier.
--
Thanks,
Sergey
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-22 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 16:09 [PATCH v5 0/5] VMX MSRs policy for Nested Virt: part 1 Sergey Dyasli
2018-02-28 16:09 ` [PATCH v5 1/5] x86/msr: add VMX MSRs definitions and populate Raw domain policy Sergey Dyasli
2018-03-21 19:52 ` Andrew Cooper
2018-03-22 9:12 ` Jan Beulich
2018-03-22 9:39 ` Sergey Dyasli [this message]
2018-02-28 16:09 ` [PATCH v5 2/5] x86/msr: add VMX MSRs into HVM_max " Sergey Dyasli
2018-03-21 20:46 ` Andrew Cooper
2018-03-22 10:14 ` Sergey Dyasli
2018-03-22 10:22 ` Andrew Cooper
2018-02-28 16:09 ` [PATCH v5 3/5] x86/cpuid: update signature of hvm_cr4_guest_valid_bits() Sergey Dyasli
2018-03-21 20:49 ` Andrew Cooper
2018-02-28 16:09 ` [PATCH v5 4/5] x86/msr: update domain policy on CPUID policy changes Sergey Dyasli
2018-03-21 20:53 ` Andrew Cooper
2018-02-28 16:09 ` [PATCH v5 5/5] x86/msr: handle VMX MSRs with guest_rd/wrmsr() Sergey Dyasli
2018-03-21 20:28 ` 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=1521711576.3556.2.camel@citrix.com \
--to=sergey.dyasli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.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.