[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60834DD80A6193F959719CF4FC5BA@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 15 Jun 2023 17:54:42 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yazen Ghannam <yazen.ghannam@....com>,
Borislav Petkov <bp@...en8.de>
CC: "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: RE: [PATCH] x86/mce: Schedule mce_setup() on correct CPU for CPER
decoding
> for_each_possible_cpu(cpu) {
> if (cpu_data(cpu).initial_apicid == lapic_id) {
> m.extcpu = cpu;
Are there any other places in the kernel where we need to find the
Linux CPU number starting from the apic id?
I briefly looked a while back when I needed this for some
debug use case and didn't find it then. But Linux changes
and maybe there are some now.
Which is a long way to say I'd like to see boot code initialize an array so the above
could just be:
m.extcpu = lapic_to_cpu[lapic_id];
But we'd need at least a couple of use cases to justify.
-Tony
Powered by blists - more mailing lists