summaryrefslogtreecommitdiff
path: root/arch/x86/include/asm/apic.h
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2024-02-14 00:05:20 +0300
committerThomas Gleixner <tglx@linutronix.de>2024-02-16 00:07:41 +0300
commit4a5f72a4a39f5d5dcf9b9dc1acc57ecbbb8d4caa (patch)
treea0d73d7cbc0b457eaec6dd9abf17c1f128ce0abd /arch/x86/include/asm/apic.h
parent58d16928358f91d48421838a7484321b3149130d (diff)
downloadlinux-4a5f72a4a39f5d5dcf9b9dc1acc57ecbbb8d4caa.tar.xz
x86/apic: Remove yet another dubious callback
Paranoia is not wrong, but having an APIC callback which is in most implementations a complete NOOP and in one actually looking whether the APICID of an upcoming CPU has been registered. The same APICID which was used to bring the CPU out of wait for startup. That's paranoia for the paranoia sake. Remove the voodoo. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Michael Kelley <mhklinux@outlook.com> Tested-by: Sohil Mehta <sohil.mehta@intel.com> Link: https://lore.kernel.org/r/20240212154640.116510935@linutronix.de
Diffstat (limited to 'arch/x86/include/asm/apic.h')
-rw-r--r--arch/x86/include/asm/apic.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/x86/include/asm/apic.h b/arch/x86/include/asm/apic.h
index 89eae0c1e552..ba219d6c851e 100644
--- a/arch/x86/include/asm/apic.h
+++ b/arch/x86/include/asm/apic.h
@@ -288,7 +288,6 @@ struct apic {
/* Probe, setup and smpboot functions */
int (*probe)(void);
int (*acpi_madt_oem_check)(char *oem_id, char *oem_table_id);
- bool (*apic_id_registered)(void);
void (*init_apic_ldr)(void);
u32 (*cpu_present_to_apicid)(int mps_cpu);