vgic_its_debug_start(9)

Okay bestie, welcome to the vgic_its_debug_start(9) page — this is the Kernel API Manual, and we are about to make a seq_file iterator feel like main character energy ✨

🎀 NAME 🎀

vgic_its_debug_start — Start function for the seq_file interface. That's the vibe: it's the starter function, periodt 💅

✨ SYNOPSIS ✨

void * vgic_its_debug_start (struct seq_file *s , loff_t *pos );

🫶 ARGUMENTS 🫶

Two args, both iconic:

• s — The seq_file structure.
• pos — The starting position (offset).

🌸 DESCRIPTION 🌸

Okay so here's the lore: this function initializes the iterator to the beginning of the ITS tables and advances it to the specified position. It also acquires the its_lock mutex to protect shared data. No cap, that mutex is doing the most to keep things safe 🔥

💖 RETURN 💖

Here's the vibe check on what comes back:

• An iterator pointer on success — slay 👑
• NULL if no devices are found or the end of the list is reached — that's the empty-list energy 😭
• ERR_PTR(-ENOMEM) on memory allocation failure — not the glow-up we wanted, but it's literally in the docs 💀

🦋 SEE ALSO 🦋

Go read these next, bestie:

• Kernel file ./arch/arm64/kvm/vgic/vgic-debug.c — the home base 🏠
• struct vgic_its_iter(9)
• end_of_iter(9)
• vgic_its_iter_next(9)
• vgic_its_debug_next(9)
• vgic_its_debug_stop(9)
• vgic_its_debug_show(9)
• vgic_its_debug_init(9)

Signed, sealed, delivered: source/version is ./arch/arm64/kvm/vgic, the date is October 2026, and the whole page is vgic_its_debug_start(9) from the Kernel API Manual — mwah 💋🫶✨