From: Jan Beulich <jbeulich@suse.com>
To: "George Dunlap" <george.dunlap@citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Jann Horn <jannh@google.com>
Subject: Re: [PATCH v2] SUPPORT.md: Un-shimmed 32-bit PV guests are no longer supported
Date: Thu, 6 May 2021 15:09:35 +0200 [thread overview]
Message-ID: <acd695c1-dc04-4606-5212-5fd993e355b1@suse.com> (raw)
In-Reply-To: <20210506124752.65844-1-george.dunlap@citrix.com>
On 06.05.2021 14:47, George Dunlap wrote:
> --- a/xen/arch/x86/Kconfig
> +++ b/xen/arch/x86/Kconfig
> @@ -55,7 +55,7 @@ config PV
> config PV32
> bool "Support for 32bit PV guests"
> depends on PV
> - default y
> + default PV_SHIM
> select COMPAT
> ---help---
> The 32bit PV ABI uses Ring1, an area of the x86 architecture which
> @@ -67,7 +67,10 @@ config PV32
> reduction, or performance reasons. Backwards compatibility can be
> provided via the PV Shim mechanism.
>
> - If unsure, say Y.
> + Note that outside of PV Shim, 32-bit PV guests are not security
> + supported anymore.
> +
> + If unsure, use the default setting.
Alongside this I wonder whether we should also default opt_pv32 to false
then, unless running in shim mode.
Jan
next prev parent reply other threads:[~2021-05-06 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 12:47 [PATCH v2] SUPPORT.md: Un-shimmed 32-bit PV guests are no longer supported George Dunlap
2021-05-06 13:09 ` Jan Beulich [this message]
2021-05-06 14:32 ` Andrew Cooper
2021-05-07 10:26 ` Roger Pau Monné
2021-05-07 11:05 ` Jan Beulich
2021-06-04 13:14 ` George Dunlap
2021-06-07 9:18 ` Jan Beulich
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=acd695c1-dc04-4606-5212-5fd993e355b1@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jannh@google.com \
--cc=roger.pau@citrix.com \
--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).