From: Andi Kleen <ak@linux.intel.com>
To: Juergen Gross <jgross@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
x86@kernel.org, Alok Kataria <akataria@vmware.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org,
Thomas Gleixner <tglx@linutronix.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH 0/2] Remove 32-bit Xen PV guest support
Date: Mon, 15 Jul 2019 09:34:00 -0700 [thread overview]
Message-ID: <87y30zfe9z.fsf@linux.intel.com> (raw)
In-Reply-To: <20190715113739.17694-1-jgross@suse.com> (Juergen Gross's message of "Mon, 15 Jul 2019 13:37:37 +0200")
Juergen Gross <jgross@suse.com> writes:
> The long term plan has been to replace Xen PV guests by PVH. The first
> victim of that plan are now 32-bit PV guests, as those are used only
> rather seldom these days. Xen on x86 requires 64-bit support and with
> Grub2 now supporting PVH officially since version 2.04 there is no
> need to keep 32-bit PV guest support alive in the Linux kernel.
> Additionally Meltdown mitigation is not available in the kernel running
> as 32-bit PV guest, so dropping this mode makes sense from security
> point of view, too.
Normally we have a deprecation period for feature removals like this.
You would make the kernel print a warning for some releases, and when
no user complains you can then remove. If a user complains you can't.
-Andi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Alok Kataria <akataria@vmware.com>
Subject: Re: [PATCH 0/2] Remove 32-bit Xen PV guest support
Date: Mon, 15 Jul 2019 09:34:00 -0700 [thread overview]
Message-ID: <87y30zfe9z.fsf@linux.intel.com> (raw)
In-Reply-To: <20190715113739.17694-1-jgross@suse.com> (Juergen Gross's message of "Mon, 15 Jul 2019 13:37:37 +0200")
Juergen Gross <jgross@suse.com> writes:
> The long term plan has been to replace Xen PV guests by PVH. The first
> victim of that plan are now 32-bit PV guests, as those are used only
> rather seldom these days. Xen on x86 requires 64-bit support and with
> Grub2 now supporting PVH officially since version 2.04 there is no
> need to keep 32-bit PV guest support alive in the Linux kernel.
> Additionally Meltdown mitigation is not available in the kernel running
> as 32-bit PV guest, so dropping this mode makes sense from security
> point of view, too.
Normally we have a deprecation period for feature removals like this.
You would make the kernel print a warning for some releases, and when
no user complains you can then remove. If a user complains you can't.
-Andi
next prev parent reply other threads:[~2019-07-15 16:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 11:37 [Xen-devel] [PATCH 0/2] Remove 32-bit Xen PV guest support Juergen Gross
2019-07-15 11:37 ` Juergen Gross
2019-07-15 11:37 ` [Xen-devel] [PATCH 1/2] x86/xen: remove " Juergen Gross
2019-07-15 11:37 ` Juergen Gross
2019-07-15 15:44 ` [Xen-devel] " Boris Ostrovsky
2019-07-15 15:44 ` Boris Ostrovsky
2019-07-16 3:52 ` [Xen-devel] " Juergen Gross
2019-07-16 3:52 ` Juergen Gross
2019-07-15 11:37 ` [PATCH 2/2] x86/paravirt: remove 32-bit support from PARAVIRT_XXL Juergen Gross
2019-07-15 11:37 ` [Xen-devel] " Juergen Gross
2019-07-15 11:37 ` Juergen Gross
2019-07-15 12:32 ` [Xen-devel] [PATCH 0/2] Remove 32-bit Xen PV guest support Peter Zijlstra
2019-07-15 12:32 ` Peter Zijlstra
2019-07-15 12:36 ` Juergen Gross
2019-07-15 12:36 ` [Xen-devel] " Juergen Gross
2019-07-15 12:36 ` Juergen Gross
2019-07-15 12:32 ` Peter Zijlstra
2019-07-15 16:34 ` Andi Kleen
2019-07-15 16:34 ` Andi Kleen [this message]
2019-07-15 16:34 ` Andi Kleen
2019-07-15 17:28 ` [Xen-devel] " Andy Lutomirski
2019-07-15 17:28 ` Andy Lutomirski
2019-07-15 17:39 ` [Xen-devel] " Andrew Cooper
2019-07-15 17:39 ` Andrew Cooper
2019-07-16 3:55 ` Juergen Gross
2019-07-16 3:55 ` Juergen Gross
2019-07-16 3:55 ` Juergen Gross
2019-07-15 17:39 ` Andrew Cooper
2019-07-15 17:42 ` Juergen Gross
2019-07-15 17:42 ` Juergen Gross
2019-07-15 17:42 ` Juergen Gross
2019-07-16 6:58 ` [Xen-devel] " Jan Beulich
2019-07-16 6:58 ` Jan Beulich
2019-07-16 6:58 ` Jan Beulich
2019-07-15 17:28 ` Andy Lutomirski
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=87y30zfe9z.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.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.