From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Jun Nakajima <jun.nakajima@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/vmx: add support for virtualize SPEC_CTRL
Date: Fri, 9 Feb 2024 14:13:05 +0100 [thread overview]
Message-ID: <ZcYk4bHo0Cytndwf@macbook> (raw)
In-Reply-To: <fe22b91e-227c-45df-a39a-dcccd8726cd3@suse.com>
On Fri, Feb 09, 2024 at 12:51:41PM +0100, Jan Beulich wrote:
> On 09.02.2024 11:45, Roger Pau Monné wrote:
> > On Thu, Feb 08, 2024 at 02:40:53PM +0100, Jan Beulich wrote:
> >> On 06.02.2024 15:25, Roger Pau Monne wrote:
> >>> @@ -2086,6 +2091,9 @@ void vmcs_dump_vcpu(struct vcpu *v)
> >>> if ( v->arch.hvm.vmx.secondary_exec_control &
> >>> SECONDARY_EXEC_VIRTUAL_INTR_DELIVERY )
> >>> printk("InterruptStatus = %04x\n", vmr16(GUEST_INTR_STATUS));
> >>> + if ( cpu_has_vmx_virt_spec_ctrl )
> >>> + printk("SPEC_CTRL mask = %#016lx shadow = %#016lx\n",
> >>> + vmr(SPEC_CTRL_MASK), vmr(SPEC_CTRL_SHADOW));
> >>
> >> #0... doesn't make a lot of sense; only e.g. %#lx does. Seeing context
> >> there's no 0x prefix there anyway. Having looked at the function the
> >> other day, I know though that there's a fair mix of 0x-prefixed and
> >> unprefixed hex numbers that are output.
> >
> > For consistency with how other MSRs are printed I should use the '0x'
> > prefix.
>
> MSRs? It's VMCS fields which are printed here.
Well, yes, but it represents a MSR value.
Thanks, Roger.
prev parent reply other threads:[~2024-02-09 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:25 [PATCH] x86/vmx: add support for virtualize SPEC_CTRL Roger Pau Monne
2024-02-08 13:40 ` Jan Beulich
2024-02-09 10:45 ` Roger Pau Monné
2024-02-09 11:51 ` Jan Beulich
2024-02-09 13:13 ` Roger Pau Monné [this message]
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=ZcYk4bHo0Cytndwf@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=wl@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.