From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 4/4] x86/xen: Drop CONFIG_XEN_PVHVM_SMP
Date: Wed, 5 Aug 2026 10:55:54 +0200 [thread overview]
Message-ID: <5febc2c0-4355-48d9-9342-52d590041500@suse.com> (raw)
In-Reply-To: <f06ccf87-c244-44a1-af82-52da3b01c334@suse.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1249 bytes --]
On 05.08.26 10:44, Jan Beulich wrote:
> On 05.08.2026 10:21, Juergen Gross wrote:
>> --- a/arch/x86/xen/Makefile
>> +++ b/arch/x86/xen/Makefile
>> @@ -37,8 +37,8 @@ obj-$(CONFIG_XEN_PVH) += enlighten_pvh.o
>> obj-$(CONFIG_EVENT_TRACING) += trace.o
>>
>> obj-$(CONFIG_SMP) += smp.o
>> +obj-$(CONFIG_SMP) += smp_hvm.o
>> obj-$(CONFIG_XEN_PV_SMP) += smp_pv.o
>> -obj-$(CONFIG_XEN_PVHVM_SMP) += smp_hvm.o
>
> Similar issue here - in a PV-only config smp_hvm.o doesn't want / shouldn't
> need building.
Note that I didn't change any functionality.
I agree that it seems a little bit strange, but in the end I believe
the current status is okay-ish. PV-only hasn't been something in upstream
Linux since Xen support was added, as PV was always meant to be an
alternative to bare metal support via paravirt patching. It might have
been possible to build a kernel not really functional on bare metal, but
this was more like the ability to build a x86 kernel not working on any
existing machine.
IMO the Xen kernel config options should allow for adding Xen-specific
features, but minimum Xen support should always have basic HVM support,
which includes the Xen specific performance enhancements.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2026-08-05 8:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:21 [PATCH 0/4] xen: cleanup config files Juergen Gross
2026-08-05 8:21 ` [PATCH 1/4] x86/xen: Remove redundant config dependency on X86_LOCAL_APIC Juergen Gross
2026-08-05 8:37 ` Jan Beulich
2026-08-05 8:40 ` Jan Beulich
2026-08-05 8:43 ` Andrew Cooper
2026-08-05 22:30 ` Stefano Stabellini
2026-08-05 8:21 ` [PATCH 2/4] xen: Drop CONFIG_XEN_PVHVM Juergen Gross
2026-08-05 8:28 ` Andrew Cooper
2026-08-05 8:36 ` Juergen Gross
2026-08-06 1:51 ` Jason Andryuk
2026-08-05 22:45 ` Stefano Stabellini
2026-08-05 8:21 ` [PATCH 3/4] xen: Drop CONFIG_XEN_AUTO_XLATE Juergen Gross
2026-08-05 8:42 ` Jan Beulich
2026-08-05 8:56 ` Juergen Gross
2026-08-05 22:47 ` Stefano Stabellini
2026-08-05 8:21 ` [PATCH 4/4] x86/xen: Drop CONFIG_XEN_PVHVM_SMP Juergen Gross
2026-08-05 8:44 ` Jan Beulich
2026-08-05 8:55 ` Juergen Gross [this message]
2026-08-05 9:04 ` Jan Beulich
2026-08-05 9:44 ` Jürgen Groß
2026-08-05 9:55 ` Jan Beulich
2026-08-05 22:49 ` Stefano Stabellini
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=5febc2c0-4355-48d9-9342-52d590041500@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®