hl_state_du...ngine_fences(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hl_state_dump_print_engine_fences — the Kernel API Manual (section 9) girlies, this one's for you ✨

okay so bestie, welcome to the hl_state_dump_print_engine_fences(9) page of the Kernel API Manual — section 9, we're in the deep kernel lore now, and honestly? it's giving documentation main character energy. 🎀

🌸 NAME 🌸

hl_state_dump_print_engine_fences — no cap, this one does exactly what it says on the tin: it prints the active fences for one specific engine. like, that engine. the one you asked for. periodt. 💅

🦋 SYNOPSIS 🦋

int hl_state_dump_print_engine_fences (struct hl_device *hdev , enum
hl_sync_engine_type engine_type , char **buf , size_t *size , size_t
*offset );

copy that exactly, bestie — don't be out here retyping the signature from memory, that's how you end up with a bug at 3am. 😭

✨ ARGUMENTS ✨

  • hdev — pointer to the device 💖 the whole vibe check starts here, struct hl_device *, this is your device, your main character.
  • engine_type — engine type to use ⚙️ an enum hl_sync_engine_type, so pick your engine and commit to it, iykyk.
  • buf — destination buffer double pointer, made to be used with hl_snprintf_resize 🎀 yes a double pointer, she's fancy like that.
  • size — pointer to the size container 📏 it's a size_t *, she holds the size, let her do her job.
  • offset — pointer to the offset container 🧚 also a size_t *, she tracks where you're at. lowkey essential, don't skip her.

🔥 SEE ALSO 🔥

the whole squad is here, and they all ate:

bestie seriously, that's the full list, every single one — I would never ghost a SEE ALSO reference. 🌈

and that's the page, gorgeous 💜 this icon of a manpage lives over in ./drivers/accel/habanalabs/common, and she's dated October 2026 — mark your calendars, she said see you then 🫶💖⭐

no cap, you're a kernel dev now. 🎀

📦 where this page comes from