From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Jun Nakajima <jun.nakajima@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH v4 2/5] x86/pv: allow reading FEATURE_CONTROL MSR
Date: Tue, 8 Sep 2020 17:52:59 +0200 [thread overview]
Message-ID: <f6e137b9-d0e6-0895-8b49-153db03e1c6e@suse.com> (raw)
In-Reply-To: <20200907103143.58845-3-roger.pau@citrix.com>
On 07.09.2020 12:31, Roger Pau Monne wrote:
> Linux PV guests will attempt to read the FEATURE_CONTROL MSR, so move
> the handling done in VMX code into guest_rdmsr as it can be shared
> between PV and HVM guests that way.
>
> Note that there's a slight behavior change and attempting to read the
> MSR when no features are available will result in a fault.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2020-09-08 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 10:31 [PATCH v4 0/5] x86: switch default MSR behavior Roger Pau Monne
2020-09-07 10:31 ` [PATCH v4 1/5] x86/svm: handle BU_CFG and BU_CFG2 with cases Roger Pau Monne
2020-09-08 15:51 ` Jan Beulich
2020-09-07 10:31 ` [PATCH v4 2/5] x86/pv: allow reading FEATURE_CONTROL MSR Roger Pau Monne
2020-09-08 15:52 ` Jan Beulich [this message]
2020-09-15 2:48 ` Tian, Kevin
2020-09-07 10:31 ` [PATCH v4 3/5] x86/pv: disallow access to unknown MSRs Roger Pau Monne
2020-09-07 10:31 ` [PATCH v4 4/5] x86/hvm: Disallow " Roger Pau Monne
2020-09-07 10:31 ` [PATCH v4 5/5] x86/msr: Drop compatibility #GP handling in guest_{rd, wr}msr() Roger Pau Monne
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=f6e137b9-d0e6-0895-8b49-153db03e1c6e@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.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.