handle_l1_dte(9)

✨ handle_l1_dte 💅

okay so bestie, this one lives in the Kernel API Manual — section 9, kernel land, very "don't talk to me unless you're writing a driver" energy 🫶

---

🌸 NAME 🌸

handle_l1_dte — the callback that handles L1 device table entries (specifically the 2 stage case, iykyk) ✨

---

🎀 SYNOPSIS 🎀

int handle_l1_dte (struct vgic_its *its , u32 id , void *addr , void
*opaque );

literally just those four args, no cap 🌈

---

💖 ARGUMENTS 💖

• its — the its handle 🎯
• id — the index of the entry inside the L1 table, so it knows which one we're on, periodt
• addr — kernel VA, as in the virtual address, not a vibe check 💀
• opaque — unused 🙈 (she's just there for the callback signature, no notes)

---

🦋 DESCRIPTION 🦋

so the L1 table entries get scanned by steps of 1 entry each time ⭐ and here's the return situation, pay attention bestie:

• return < 0 if there's an error 😭
• return 0 if the last dte was found while scanning the L2 table 👑
• return +1 otherwise — meaning the next L1 entry has to be scanned, keep it moving 💅

---

🔥 SEE ALSO 🔥

kernel file ./arch/arm64/kvm/vgic/vgic-its.c, plus the whole friend group:

• struct vgic_its_abi(9)
• vgic_its_invall(9)
• entry_fn_t(9)
• scan_its_table(9)
• vgic_its_restore_ite(9)
• vgic_its_restore_itt(9)
• vgic_its_save_dte(9)
• vgic_its_restore_dte(9)

---

and that's the whole page, bestie, ate and left no crumbs 🍓 this one ships out of ./arch/arm64/kvm/vgic and the date on it is October 2026, so yeah — future-coded footer, iconic behavior honestly 💜✨🎀