[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5b8f9c89f7015fa80c966c6c7f6fa259db6744f8.camel@infradead.org>
Date: Tue, 21 Feb 2023 08:35:05 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Oleksandr Natalenko <oleksandr@...alenko.name>
Cc: Kim Phillips <kim.phillips@....com>, tglx@...utronix.de,
Usama Arif <usama.arif@...edance.com>, arjan@...ux.intel.com,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
hpa@...or.com, x86@...nel.org, pbonzini@...hat.com,
paulmck@...nel.org, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, rcu@...r.kernel.org, mimoja@...oja.de,
hewenliang4@...wei.com, thomas.lendacky@....com, seanjc@...gle.com,
pmenzel@...gen.mpg.de, fam.zheng@...edance.com,
punit.agrawal@...edance.com, simon.evans@...edance.com,
liangma@...ngbit.com,
"Limonciello, Mario" <Mario.Limonciello@....com>,
Piotr Gorski <piotrgorski@...hyos.org>
Subject: Re: [PATCH v9 0/8] Parallel CPU bringup for x86_64
On Tue, 2023-02-21 at 09:25 +0100, Oleksandr Natalenko wrote:
>
>
> Right, sorry. Here it is: http://ix.io/4oLq
$ echo `grep ^00000001 4oLq | cut -c36-37`
00 02 04 06 08 0a 0c 0e 10 12 14 16 18 1a 1c 1e 01 03 05 07 09 0b 0d 0f
11 13 15 17 19 1b 1d 1f
Well they look sane enough. All even APIC IDs and then all the odd ones
is a topology that isn't massively surprising.
Does it match what you get *before* suspend/resume?
Obviously we could stick our fingers in our ears and go "la la la" and
just disable it for non-X2APIC, for AMD without X2APIC, or perhaps
disable it on *resume* but still use it at boot. But I'd really like to
understand what's going on and not do voodoo. Thanks for helping!
Download attachment "smime.p7s" of type "application/pkcs7-signature" (5965 bytes)
Powered by blists - more mailing lists