From: "Arnd Bergmann" <arnd@arndb.de>
To: "Lukas Bulwahn" <lbulwahn@redhat.com>,
"Juergen Gross" <jgross@suse.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lukas Bulwahn" <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] xen: Kconfig: Drop reference to obsolete configs MCORE2 and MK8
Date: Mon, 03 Mar 2025 10:53:43 +0100 [thread overview]
Message-ID: <c4f1640e-3046-4ad4-accf-bdfa97a3ce17@app.fastmail.com> (raw)
In-Reply-To: <20250303093759.371445-1-lukas.bulwahn@redhat.com>
On Mon, Mar 3, 2025, at 10:37, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit f388f60ca904 ("x86/cpu: Drop configuration options for early 64-bit
> CPUs") removes the config symbols MCORE2 and MK8.
>
> With that, the references to those two config symbols in xen's x86 Kconfig
> are obsolete. Drop them.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Good catch!
> diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
> index 77e788e928cd..98d8a50d2aed 100644
> --- a/arch/x86/xen/Kconfig
> +++ b/arch/x86/xen/Kconfig
> @@ -9,7 +9,7 @@ config XEN
> select PARAVIRT_CLOCK
> select X86_HV_CALLBACK_VECTOR
> depends on X86_64 || (X86_32 && X86_PAE)
> - depends on X86_64 || (X86_GENERIC || MPENTIUM4 || MCORE2 || MATOM || MK8)
> + depends on X86_64 || (X86_GENERIC || MPENTIUM4 || MATOM)
> depends on X86_LOCAL_APIC && X86_TSC
> help
> This is the Linux Xen port. Enabling this will allow the
I suspect some or all all of the other three options should be
dropped as well, given that 32-bit XEN_PV guests are already
unsupported as of
commit a13f2ef168cb2a033a284eb841bcc481ffbc90cf
Author: Juergen Gross <jgross@suse.com>
Date: Mon Jun 29 10:35:39 2020 +0200
x86/xen: remove 32-bit Xen PV guest support
Xen is requiring 64-bit machines today and since Xen 4.14 it can be
built without 32-bit PV guest support. There is no need to carry the
burden of 32-bit PV guest support in the kernel any longer, as new
guests can be either HVM or PVH, or they can use a 64 bit kernel.
Remove the 32-bit Xen PV support from the kernel.
and 32-bit Pentium4 and Atom CPUs don't run modern Xen hosts.
Most likely this should be
depends on X86_64 || (X86_32 && X86_PAE && X86_GENERIC)
to say that running 32-bit XEN_PVHVM guests is still supported
allowed on 64-bit hosts, but not on pure 32-bit machines.
Arnd
next prev parent reply other threads:[~2025-03-03 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 9:37 [PATCH] xen: Kconfig: Drop reference to obsolete configs MCORE2 and MK8 Lukas Bulwahn
2025-03-03 9:45 ` Juergen Gross
2025-03-03 9:53 ` Arnd Bergmann [this message]
2025-03-03 10:23 ` [tip: x86/cpu] " tip-bot2 for Lukas Bulwahn
2025-03-04 10:26 ` tip-bot2 for Lukas Bulwahn
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=c4f1640e-3046-4ad4-accf-bdfa97a3ce17@app.fastmail.com \
--to=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox