acpi_evaluate_ost(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_evaluate_ost(9) β€” like, the Kernel API Manual entry, bestie ✨

okay so this is acpi_evaluate_ost, and it lives in section 9 of the kernel API manual (yes, the man-page-y one). it's short, it's sweet, and if you're writing an ACPI hotplug handler you literally cannot skip it. no cap. 🫢


🌸 NAME 🌸

acpi_evaluate_ost β€” evaluates _OST for hotplug operations πŸ’–

✨ SYNOPSIS ✨

acpi_status acpi_evaluate_ost (acpi_handle handle , u32 source_event ,
u32 status_code , struct acpi_buffer *status_buf );

πŸŽ€ ARGUMENTS πŸŽ€

  • handle β€” the ACPI device handle. the whole "who are we talking about" of it all πŸ‘‘
  • source_event β€” the source event code πŸ¦‹
  • status_code β€” the status code 🌸
  • status_buf β€” optional detailed information, and it's NULL if there's none. so like, optional-optional πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

so the entire job here is: evaluate _OST for hotplug operations. that's it. that's the vibe check. ✨

real talk though: every single ACPI hotplug handler must call this function when it's evaluating _OST for hotplug operations. not "should", not "if you feel like it" β€” must. periodt. πŸ’…

and the genuinely iconic part? when the platform doesn't support _OST, this function literally has no effect. it just quietly does nothing. no error, no drama, no mess. lowkey the most well-adjusted function in the kernel 😭🫢

🌈 SEE ALSO 🌈

kernel file ./drivers/acpi/utils.c, and honestly the whole friend group:


mwah πŸ’‹ that's the whole page. shipped from ./drivers/acpi, dated October 2026, and yeah β€” it's giving reference manual, it's giving hotplug royalty. go call your _OST. 🧚⭐

πŸ“¦ where this page comes from