From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Michal Pecio <michal.pecio@gmail.com>,
Eric DeVolder <eric.devolder@oracle.com>
Subject: Re: [PATCH] x86/acpi/boot: Correct acpi_is_processor_usable() check again
Date: Thu, 13 Nov 2025 08:55:29 -0600 [thread overview]
Message-ID: <a9111a91-33e4-4f07-96c8-5d724a8429f1@amd.com> (raw)
In-Reply-To: <20251113143408.GCaRXsYM8aVHLN3zSj@fat_crate.local>
On 11/13/25 8:34 AM, Borislav Petkov wrote:
> On Thu, Nov 13, 2025 at 08:30:27AM -0600, Mario Limonciello wrote:
>>> + /*
>>> + * QEMU expects legacy "Enabled=0" LAPIC entries to be counted as usable
>>> + * in order to support CPU hotplug in guests.
>>> + */
>>
>> I think it would be good to amend this comment to indicate that the behavior
>> of the "enabled bit" changed and that QEMU follows the newer behavior but
>> advertises the older version.
>
> This is just there to hint why we're doing this fix to the kernel - i.e.,
> try to salvage an already shit situation. Any other deviation from the spec is
> not the kernel's problem.
>
OK.
next prev parent reply other threads:[~2025-11-13 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 14:53 Yazen Ghannam
2025-11-12 13:56 ` Borislav Petkov
2025-11-12 16:35 ` Mario Limonciello
2025-11-12 17:21 ` Borislav Petkov
2025-11-13 14:27 ` Borislav Petkov
2025-11-13 14:30 ` Mario Limonciello
2025-11-13 14:34 ` Borislav Petkov
2025-11-13 14:55 ` Mario Limonciello [this message]
2025-11-12 18:05 ` Michal Pecio
2025-11-12 19:17 ` Borislav Petkov
2025-11-14 16:23 ` Ricardo Neri
2025-11-14 16:53 ` Borislav Petkov
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=a9111a91-33e4-4f07-96c8-5d724a8429f1@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=eric.devolder@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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®