From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <jbeulich@suse.com>
Cc: "Simon Gaiser" <simon@invisiblethingslab.com>,
"committers@xenproject.org" <committers@xenproject.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH] x86/ACPI: Ignore entries with invalid APIC IDs when parsing MADT
Date: Tue, 12 Sep 2023 09:56:51 +0200 [thread overview]
Message-ID: <874jjz3juk.ffs@tglx> (raw)
In-Reply-To: <27ae69b6-bc57-dee3-2528-8311a38decda@citrix.com>
On Mon, Sep 11 2023 at 19:24, Andrew Cooper wrote:
> Furthermore, cursory testing that Thomas did for the Linux topology work
> demonstrates that it is broken anyway for reasons unrelated to ACPI parsing.
>
> Even furthermore, it's an area of the Xen / dom0 boundary which is
> fundamentally broken for non-PV cases, and undocumented for the PV case,
> hence why it's broken in Linux.
>
> Physical CPU Hotplug does not pass the bar for being anything more than
> experimental. It's absolutely not tech-preview level because the only
> demo it has had in an environment (admittedly virtual) which does
> implement the spec in a usable way demonstrates that it doesn't function.
>
> The fact no-one has noticed until now shows that the feature isn't used,
> which comes back around full circle to the fact that Intel never made it
> work and never shipped it.
OTOH it _is_ used in virtualization. KVM supports it and it just
works. That's how I found out that XEN explodes in colourful ways :)
Thanks,
tglx
next prev parent reply other threads:[~2023-09-12 7:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 9:38 [XEN PATCH] x86/ACPI: Ignore entries with invalid APIC IDs when parsing MADT Simon Gaiser
2023-08-07 10:01 ` Andrew Cooper
2023-08-07 10:06 ` Andrew Cooper
2023-08-07 10:17 ` Simon Gaiser
2023-08-07 14:45 ` Simon Gaiser
2023-08-23 9:32 ` Andrew Cooper
2023-09-11 10:17 ` Simon Gaiser
2023-08-07 10:13 ` Jan Beulich
2023-08-07 12:55 ` Simon Gaiser
2023-08-07 13:17 ` Jan Beulich
2023-08-07 14:04 ` Andrew Cooper
2023-08-07 14:18 ` Jan Beulich
2023-08-23 9:21 ` Andrew Cooper
2023-08-23 12:56 ` Jan Beulich
2023-08-27 15:44 ` Thomas Gleixner
2023-08-29 14:25 ` Roger Pau Monné
2023-08-29 22:54 ` Thomas Gleixner
2023-08-30 7:20 ` Jan Beulich
2023-08-30 15:44 ` Thomas Gleixner
2023-08-07 15:05 ` Simon Gaiser
2023-08-23 9:13 ` Roger Pau Monné
2023-09-01 7:44 ` Jan Beulich
2023-09-06 20:49 ` Stefano Stabellini
2023-09-07 6:50 ` Jan Beulich
2023-09-07 21:30 ` Stefano Stabellini
2023-09-11 18:24 ` Andrew Cooper
2023-09-11 22:38 ` Stefano Stabellini
2023-09-12 9:38 ` Roger Pau Monné
2023-09-12 7:56 ` Thomas Gleixner [this message]
2023-09-13 10:02 ` George Dunlap
2023-09-13 23:18 ` Stefano Stabellini
2023-09-15 10:41 ` George Dunlap
2023-09-12 8:33 ` Jan Beulich
2023-09-12 8:36 ` Jan Beulich
2023-09-11 18:05 ` Simon Gaiser
2023-09-12 8:41 ` Jan Beulich
2023-09-12 8:45 ` 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=874jjz3juk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=simon@invisiblethingslab.com \
--cc=sstabellini@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.