npu_busy_time_us(9)

💅 npu_busy_time_us 💅

okay so this is npu_busy_time_us(9) and it lives in the Kernel API Manual ✨ welcome to the group chat, bestie 🫶

🌸 DESCRIPTION 🌸

Okay so npu_busy_time_us is literally the time that the device spent executing jobs. That’s the whole vibe 💖

The way it works: the time is counted when and only when there are jobs submitted to firmware. No jobs to firmware? Then no ticking, periodt ⏱️

This time can be used to measure the utilization of NPU, bestie, and there are two cute ways to do it:

• calculating the npu_busy_time_us difference between two timepoints (i.e. measuring the time that the NPU was active during some workload) 🦋
• monitoring utilization percentage by reading npu_busy_time_us periodically 🌈

when you’re reading the value periodically, it shouldn’t be read too often 😭 because it may have an impact on job submission performance. The recommended period is 1 second ⭐

🔎 SEE ALSO 🔎

• Kernel file ./drivers/accel/ivpu/ivpu_sysfs.c npu_memory_utilization(9), sched_mode(9), NPU frequency control and information(9) 💜

okay that’s the whole page, mwah 💋 — signed off from ./drivers/accel/ivpu 💖, dated October 2026 ✨, and yes it’s still npu_busy_time_us(9) bestie 🎀