From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>, Eric DeVolder <eric.devolder@oracle.com>
Cc: rafael@kernel.org, lenb@kernel.org, tglx@linutronix.de,
mingo@redhat.com, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, kvijayab@amd.com,
miguel.luis@oracle.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCH 1/1] x86/acpi: acpi_is_processor_usable() dropping possible cpus
Date: Wed, 29 Mar 2023 14:34:02 -0500 [thread overview]
Message-ID: <cb5ba93f-fd0b-3858-b801-2546d821a637@amd.com> (raw)
In-Reply-To: <20230327202545.GEZCH7yUqcsddJx7Y5@fat_crate.local>
On 3/27/2023 15:25, Borislav Petkov wrote:
> On Mon, Mar 27, 2023 at 03:07:23PM -0500, Eric DeVolder wrote:
>> https://ueif.org/sites/default/files/resources/ACPI_6_3_May16.pdf
>> Section 5.2.12 MADT. Table 5-43 is the MADT Revision is numbered 5.
>> However, ACPI 6.x specs got a little "sloppy" with Revision,
>
> Yes, I've found what you're pointing out too. But exactly because of
> this sloppiness I'd like to see this more explicitly. Because we're
> basing functionality off of it and it is not some meaningless
> paperweight anymore.
>
Boris and I talked offline and got the situation clarified.
The corrected patch for MADT version handling is sent here:
https://lore.kernel.org/linux-pm/20230329174536.6931-1-mario.limonciello@amd.com/T/#u
Eric - Your patch is still needed though.
next prev parent reply other threads:[~2023-03-29 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 19:10 [PATCH 0/1] " Eric DeVolder
2023-03-27 19:10 ` [PATCH 1/1] " Eric DeVolder
2023-03-27 19:57 ` Borislav Petkov
2023-03-27 20:07 ` Eric DeVolder
2023-03-27 20:25 ` Borislav Petkov
2023-03-29 19:34 ` Limonciello, Mario [this message]
2023-03-29 19:35 ` Limonciello, Mario
2023-03-30 9:33 ` [tip: x86/urgent] x86/acpi/boot: Correct acpi_is_processor_usable() check tip-bot2 for Eric DeVolder
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=cb5ba93f-fd0b-3858-b801-2546d821a637@amd.com \
--to=mario.limonciello@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eric.devolder@oracle.com \
--cc=hpa@zytor.com \
--cc=kvijayab@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.luis@oracle.com \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®