From: Jan Beulich <jbeulich@suse.com>
To: George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] SUPPORT.md: Un-shimmed 32-bit PV guests are no longer supported
Date: Mon, 7 Jun 2021 11:18:01 +0200 [thread overview]
Message-ID: <ce26e02d-e784-4c07-3061-36f64ed7d287@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
The tool stack side change that Jürgen has just sent will only address
the smoke test side of the resulting fallout. Unless steps get taken to
continue to build Xen with PV32=y in osstest (despite the changed
default), I expect many (all?) of the test-amd64-i386-* to then fail
when doing a full flight, as otherwise a 32-bit Dom0 then also won't be
usable anymore. Of course I think I recall the question having got
raised in the past whether the 32-bit Dom0 testing shouldn't be dropped
at some point. Yet even then I suppose some 32-bit DomU testing would
still want keeping, which still would require a PV32=y hypervisor.
I guess we want to postpone backporting until that is sorted.
Jan
prev parent reply other threads:[~2021-06-07 9:18 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
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 [this message]
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=ce26e02d-e784-4c07-3061-36f64ed7d287@suse.com \
--to=jbeulich@suse.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.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).