apic_soft_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… apic_soft_disable β€” a kernel API manual moment (section 9 of the kernel API manual, bestie)

okay so you found your way to apic_soft_disable(9) and honestly? iconic. this is the Kernel API Manual and we're about to get into it. πŸŽ€


✨ NAME ✨

apic_soft_disable β€” clears and software-disables the local APIC on hotplug. literally that's the whole job. no cap. πŸ¦‹


🌸 SYNOPSIS 🌸

void apic_soft_disable (void );

πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. that's it. zero. none. the void is voiding. πŸ’€

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea β˜• β€” unlike disable_local_APIC, this function does not touch the enable bit in MSR_IA32_APICBASE. not even a little. hands off. πŸ™ˆ

why, you ask? because clearing that bit on systems based on the 3 wire APIC bus would require a hardware reset, since the APIC would lose track of bus arbitration. like, the whole vibe would be ruined and you can't just undo it. 😭

now, on systems with FSB delivery, APICBASE could be disabled β€” but only if it's guaranteed that no interrupt is sent to the APIC while it's in that state. and here's the messy part: it's not clear from the SDM whether it still responds to INIT/SIPI messages. 🫠 so we stay on the safe side and use software disable. periodt. πŸ’…

ngl bestie, the whole energy here is "we could, but should we?" and the answer is no. safe side only. 🧚

⭐ SEE ALSO ⭐


and that's the whole page, bestie! 🫢 this one lives in ./arch/x86/kernel/apic and it's dated October 2026 β€” so like, future vibes. go read the other APIC pages, they ate. πŸ‘‘πŸŒˆπŸ’–

πŸ“¦ where this page comes from