xe_hw_engin...s_sysfs_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

xe_hw_engine_class_sysfs_init β€” init HW engine classes on GT πŸ’…

(also hi bestie, this page is straight out of the Kernel API Manual, section 9, and it's giving very much "small function, big responsibilities" energy πŸ¦‹)


✨ SYNOPSIS ✨

int xe_hw_engine_class_sysfs_init (struct xe_gt *gt );

🌸 ARGUMENTS 🌸

  • gt β€” the Xe GT. that's it, that's the whole argument. one (1) thing. iconic of it honestly πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea β˜• β€” this routine creates sysfs for HW engine classes, and then it adds methods to get/set different scheduling properties for HW engine class.

so like: sysfs gets built, and then the scheduling-property getters and setters come along for the ride. both things, one function, no cap. 🫢


πŸ”₯ RETURN πŸ”₯

  • returns an error value when it fails 😭
  • returns 0 for success πŸŽ‰

(vibe check: zero means we ate. anything else means we did not. πŸ’€)


πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.c β€” the actual home of this whole situation
  • xe_hw_engine_timeout_in_range(9) β€” another page, go read it, iykyk ✨

ngl bestie, if you're calling this, double-check your struct xe_gt * first β€” passing a bogus pointer is not the main character move you think it is πŸ™ˆ

later besties πŸ’œ β€” this one comes to you from ./drivers/gpu/drm/xe, dated October 2026, and yeah, the page header still says xe_hw_engin...s_sysfs_init(9) because even kernel docs get a little truncated sometimes 😭✌️

πŸ“¦ where this page comes from