cpuhp_setup_state_nocalls(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so cpuhp_setup_state_nocalls β€” from the Kernel API Manual, bestie β€” is literally β€œSetup hotplug state callbacks without calling the @startup callback”. That’s the whole assignment. ✨


🌸 SYNOPSIS 🌸

int cpuhp_setup_state_nocalls (enum cpuhp_state state , const char *name , int (*startup)(unsigned int cpu) , int (*teardown)(unsigned int cpu) );

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the state for which the calls are installed. that’s the vibe check for where this callback setup lives πŸ’«
  • name β€” name of the callback. yes, it needs a name, bestie 🏷️
  • startup β€” startup callback function or NULL if not required. so if you don’t need it, pass NULL and keep it moving 🫢
  • teardown β€” teardown callback function or NULL if not required. same deal: NULL is totally valid if you’re not using it πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

Same as cpuhp_setup_state except that the startup callback is not invoked during installation. so it’s giving β€œsetup state callbacks, but make it no-startup-call” energy 😌

NOP if SMP=n or HOTPLUG_CPU=n. no cap, that’s the condition, periodt. πŸ’€


πŸ’œ SEE ALSO πŸ’œ

start with the kernel file ./include/linux/cpuhotplug.h, then go off bestie:


mwah πŸ’‹ this page came from ./include/linux, dated October 2026, and it’s serving Kernel API Manual realness β€” bye bestie, go slay your hotplug setup 🫢✨

πŸ“¦ where this page comes from