From: "Woodhouse, David" <dwmw@amazon.co.uk>
To: "jgross@suse.com" <jgross@suse.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"Veith, Simon" <sveith@amazon.de>
Subject: Re: [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel()
Date: Wed, 11 Jul 2018 09:15:03 +0000 [thread overview]
Message-ID: <1531300502.8759.24.camel@amazon.co.uk> (raw)
In-Reply-To: <20180530110958.19413-3-jgross@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
On Wed, 2018-05-30 at 13:09 +0200, Juergen Gross wrote:
> There is no need to set the same capabilities for each cpu
> individually. This can easily be done for all cpus when starting the
> kernel.
>
> Upstream commit: 0808e80cb760de2733c0527d2090ed2205a1eef8 ("xen: set
> cpu capabilities from xen_start_kernel()")
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
That breaks PV guests because they get KAISER enabled — when
kaiser_check_boottime_disable() runs, X86_FEATURE_XENPV isn't set.
Simon is testing, and about to send a fix...
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5210 bytes --]
[-- Attachment #2.1: Type: text/plain, Size: 215 bytes --]
Amazon Development Centre (London) Ltd. Registered in England and Wales with registration number 04543232 with its registered office at 1 Principal Place, Worship Street, London EC2A 2FA, United Kingdom.
[-- Attachment #2.2: Type: text/html, Size: 228 bytes --]
[-- Attachment #3: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-11 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180530110958.19413-1-jgross@suse.com>
2018-05-30 11:09 ` [PATCH 1/3] x86/amd: revert commit 944e0fc51a89c9827b9 Juergen Gross
2018-05-30 11:09 ` [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel() Juergen Gross
2018-05-30 11:09 ` [PATCH 3/3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen Juergen Gross
2018-06-02 13:11 ` [PATCH 0/3] Correct 4.9 stable commit 944e0fc51a89c98 Greg KH
[not found] ` <20180530110958.19413-3-jgross@suse.com>
2018-06-02 13:35 ` Patch "xen: set cpu capabilities from xen_start_kernel()" has been added to the 4.9-stable tree gregkh
2018-07-11 9:15 ` Woodhouse, David [this message]
2018-07-11 9:46 ` [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel() Juergen Gross
[not found] ` <b1933a71-360e-c046-a6aa-42e4b047bcbd@suse.com>
2018-07-11 9:54 ` Woodhouse, David
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=1531300502.8759.24.camel@amazon.co.uk \
--to=dwmw@amazon.co.uk \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=stable@vger.kernel.org \
--cc=sveith@amazon.de \
--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).