All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
	Anthony PERARD <anthony.perard@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH v2 for-4.15] x86/msr: introduce an option for HVM relaxed rdmsr behavior
Date: Thu, 4 Mar 2021 18:09:58 -0500	[thread overview]
Message-ID: <9fa2be52-9d1a-e841-5bb4-3180b4b5b033@oracle.com> (raw)
In-Reply-To: <20210304144755.35891-1-roger.pau@citrix.com>


On 3/4/21 9:47 AM, Roger Pau Monne wrote:
> Introduce an option to allow selecting a less strict behaviour for
> rdmsr accesses targeting a MSR not explicitly handled by Xen. Since
> commit 84e848fd7a162f669 accesses to MSRs not explicitly handled by
> Xen result in the injection of a #GP to the guest. This is a behavior
> change since previously a #GP was only injected if accessing the MSR
> on the real hardware will also trigger a #GP.
>
> This commit attempts to offer a fallback option similar to the
> previous behavior. Note however that the value of the underlying MSR
> is never leaked to the guest, as the newly introduced option only
> changes whether a #GP is injected or not.
>
> Long term the plan is to properly handle all the MSRs, so the option
> introduced here should be considered a temporary resort for OSes that
> don't work properly with the new MSR policy. Any OS that requires this
> option to be enabled should be reported to
> xen-devel@lists.xenproject.org.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> ---
> Changes since v1:
>  - Only apply the option to HVM guests.
>  - Only apply the special handling to MSR reads.
>  - Sanitize the newly introduced flags field.
>  - Print a warning message when the option is used.
> ---
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> ---
> Boris, could you please test with Solaris to see if this fixes the
> issue?


Yes, still works. (It worked especially well after I noticed new option name ;-))


-boris




  parent reply	other threads:[~2021-03-04 23:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 14:47 [PATCH v2 for-4.15] x86/msr: introduce an option for HVM relaxed rdmsr behavior Roger Pau Monne
2021-03-04 14:59 ` Ian Jackson
2021-03-04 15:13   ` Roger Pau Monné
2021-03-04 15:20     ` Ian Jackson
2021-03-04 16:55       ` Roger Pau Monné
2021-03-04 17:13         ` Ian Jackson
2021-03-04 17:43           ` Roger Pau Monné
2021-03-04 18:21             ` Ian Jackson
2021-03-05 10:26             ` Jan Beulich
2021-03-04 23:09 ` Boris Ostrovsky [this message]
2021-03-04 23:28   ` Andrew Cooper
2021-03-05  8:26     ` Roger Pau Monné
2021-03-05  0:06 ` Andrew Cooper
2021-03-05  9:15   ` Roger Pau Monné
2021-03-05 10:35     ` Jan Beulich
2021-03-05 10:56 ` Jan Beulich
2021-03-05 11:06   ` Jan Beulich
2021-03-08 14:30   ` Roger Pau Monné

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=9fa2be52-9d1a-e841-5bb4-3180b4b5b033@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.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.