From: Ian Jackson <iwj@xenproject.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: <xen-devel@lists.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>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH RFC for-4.15] x86/msr: introduce an option for legacy MSR behavior selection
Date: Mon, 1 Mar 2021 17:57:06 +0000 [thread overview]
Message-ID: <24637.10994.995547.72710@mariner.uk.xensource.com> (raw)
In-Reply-To: <YD0pwgN3jOYTGWnH@Air-de-Roger>
Roger Pau Monné writes ("Re: [PATCH RFC for-4.15] x86/msr: introduce an option for legacy MSR behavior selection"):
> On Mon, Mar 01, 2021 at 05:16:34PM +0000, Ian Jackson wrote:
> > So AIUI this patch is to make it possible for Xen 4.15 to behave like
> > Xen 4.14, thus avoiding a regression for these troublesome guests.
>
> Yes, sorry I haven't provided a release executive summary, as I wasn't
> sure this would be acceptable in it's current form. Can do if there's
> consensus this is an acceptable fix.
Thanks for the information. I am in favour of fixing this issue.
I have it on my 4.15 blockers list.
Thanks,
Ian.
next prev parent reply other threads:[~2021-03-01 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:23 [PATCH RFC for-4.15] x86/msr: introduce an option for legacy MSR behavior selection Roger Pau Monne
2021-03-01 17:16 ` Ian Jackson
2021-03-01 17:52 ` Roger Pau Monné
2021-03-01 17:57 ` Ian Jackson [this message]
2021-03-01 19:33 ` Boris Ostrovsky
2021-03-04 14:02 ` Andrew Cooper
2021-03-04 14:17 ` Andrew Cooper
2021-03-02 11:16 ` Jan Beulich
2021-03-02 15:00 ` Roger Pau Monné
2021-03-02 15:18 ` Jan Beulich
2021-03-03 15:38 ` Roger Pau Monné
2021-03-04 8:48 ` Jan Beulich
2021-03-04 10:05 ` Roger Pau Monné
2021-03-04 10:58 ` Jan Beulich
2021-03-04 11:24 ` Ian Jackson
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=24637.10994.995547.72710@mariner.uk.xensource.com \
--to=iwj@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--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 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).