From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>,
"Zhang, Rui" <rui.zhang@intel.com>
Cc: "Brown, Len" <len.brown@intel.com>,
"zhang.jia@linux.alibaba.com" <zhang.jia@linux.alibaba.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores
Date: Mon, 20 Feb 2023 23:52:06 +0100 [thread overview]
Message-ID: <87bkloosq1.ffs@tglx> (raw)
In-Reply-To: <Y/PEnzRCZXA94cuw@hirez.programming.kicks-ass.net>
On Mon, Feb 20 2023 at 20:06, Peter Zijlstra wrote:
> On Mon, Feb 20, 2023 at 02:33:09PM +0000, Zhang, Rui wrote:
> APIC-ID is of no use vs hybrid though, and MADT doesn't include any
> either, so that's all still buggered.
>
> Luckily it looks like MADT is fairly extensible, ideally we add an field
> to entry-type-0 to help with the hybrid mess.
I don't think that's the right way. This should use PPTT because that's
a proper hierarchy model. Extending MADT is just another duct tape
solution.
And it actually does not matter which way we go because none of the
existing systems have any of that.
Thanks,
tglx
next prev parent reply other threads:[~2023-02-20 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 3:28 [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores Zhang Rui
2023-02-20 3:28 ` [PATCH V2 1/1] x86/topology: fix erroneous smp_num_siblings on Intel Hybrid platform Zhang Rui
2023-02-20 11:22 ` Peter Zijlstra
2023-02-21 8:34 ` Zhang, Rui
2023-03-13 2:05 ` Zhang, Rui
2023-02-20 10:36 ` [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores Peter Zijlstra
2023-02-20 14:40 ` Zhang, Rui
2023-02-20 11:08 ` Peter Zijlstra
2023-02-20 14:33 ` Zhang, Rui
2023-02-20 19:06 ` Peter Zijlstra
2023-02-20 22:52 ` Thomas Gleixner [this message]
2023-02-21 8:01 ` Zhang, Rui
2023-02-20 22:49 ` Thomas Gleixner
2023-02-21 8:26 ` Zhang, Rui
2023-03-07 16:10 ` Zhang, Rui
2023-03-08 2:46 ` Brown, Len
2023-02-21 9:00 ` Peter Zijlstra
2023-02-21 10:09 ` 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=87bkloosq1.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=x86@kernel.org \
--cc=zhang.jia@linux.alibaba.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