vgic_its_invall(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vgic_its_invall(9) β€” from the Kernel API Manual, bestie πŸŽ€

Okay so picture this: you're deep in the kernel, arm64 edition, and you need to nuke some LPIs. This page is your girl. It's vgic_its_invall, straight out of the Kernel API Manual, and honestly? iconic. ✨


🌸 NAME 🌸

vgic_its_invall β€” invalidate all LPIs targeting a given vcpu. all of them. every last one. periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int vgic_its_invall (struct kvm_vcpu *vcpu );

(it returns an int, she's giving main character energy, we love a return value 🫢)


πŸŽ€ ARGUMENTS πŸŽ€

  • vcpu β€” the vcpu for which the RD is targeted by an invalidation. like, that's the vcpu. the one the RD is aimed at. no cap. πŸ’–

✨ DESCRIPTION ✨

So here's the tea, and it's lowkey important: contrary to the INVALL command, this targets a RD instead of a collection. different target, different vibe. πŸ¦‹

And because of that β€” plot twist β€” we don't need to hold the its_lock, since no ITS is involved here. that's it. that's the whole reason. no lock, no stress, no drama. 😌✨

fr fr though β€” this is genuinely why the lock isn't needed, not me being lazy. the ITS just isn't in the picture here. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

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

go read them, they're all slay in their own way 🌈⭐


and that's the page!! mwah πŸ’‹ this little cutie lives in ./arch/arm64/kvm/vgic, dated October 2026 β€” screenshot it, cite it, put it on your fridge, iykyk πŸ“πŸ§šπŸ’œ

πŸ“¦ where this page comes from