cpuhp_remov...s_cpuslocked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cpuhp_remov...s_cpuslocked(9) β€” Kernel API Manual, bestie! πŸŽ€

okay so real talk, we're deep in the kernel hotplug docs rn and this one is ✨niche✨ but it's giving main character energy for anyone doing CPU hotplug while already holding a lock. Let's get into it 🫢


✨ NAME ✨

cpuhp_remove_state_nocalls_cpuslocked β€” the one that yanks out hotplug state callbacks and doesn't invoke the teardown, and you're only allowed to call it from inside a region held by cpus_read_lock(). no cap, that's the whole vibe check πŸ’…


🌸 SYNOPSIS 🌸

void cpuhp_remove_state_nocalls_cpuslocked (enum cpuhp_state state );

literally one arg, one return type, that's it. slay ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • state β€” the state whose calls get removed. like, this is which hotplug state you're tearing down the callbacks for. iconic little enum πŸŽ€

πŸ’– DESCRIPTION πŸ’–

okay so it's the same as cpuhp_remove_state nocalls, bestie β€” literally the same deal β€” except you must invoke it from within a region held by cpus_read_lock(). that's the whole difference and the whole personality. "cpuslocked" in the name is not decorative, it's a promise, iykyk πŸ”₯

⚠️ lowkey important: if you're not inside a cpus_read_lock held region, this is not the function for you. the name is screaming it at you fr fr 😭

🌈 SEE ALSO 🌈

so there's a whole friend group here, and the kernel file ./include/linux/cpuhotplug.h is where they all hang out πŸ‘‘

plus the source lives at Kernel file ./include/linux/cpuhotplug.h β€” go read the header, it ate πŸ’€βœ¨


anyway that's the page, mwah πŸ’‹ β€” this little drop came from ./include/linux, dated October 2026, and it's filed under cpuhp_remov...s_cpuslocked(9). go forth and hold that read lock responsibly bestie πŸŒΈπŸ¦‹πŸ’œ

πŸ“¦ where this page comes from