entry_fn_t(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« entry_fn_t(9) β€” like, the Kernel API Manual page, bestie πŸ’«

okay so picture this: you're deep in the kernel, you're restoring a table, and something needs to happen for every single entry. that something? it's this callback. entry_fn_t is literally the callback that gets called on a table entry restore path. no cap. πŸŽ€


✨ NAME ✨

entry_fn_t β€” the callback that gets called on a table entry restore path. yes that's the whole vibe. it's giving "small but crucial". πŸ‘‘


🌸 SYNOPSIS 🌸

int entry_fn_t (struct vgic_its *its , u32 id , void *entry , void
*opaque );

literally just one function signature, but she's iconic. πŸ¦‹


πŸ’… ARGUMENTS πŸ’…

  • its β€” the its handle. your main character struct, fr fr. πŸ’–
  • id β€” the id of the entry. gotta know which one we're talking about, obviously. ⭐
  • entry β€” pointer to the entry. this is the actual thing, the moment, the whole point. 🌈
  • opaque β€” pointer to an opaque data. mysterious. unknowable. we love her. πŸ™ˆ

πŸ”₯ RETURN πŸ”₯

okay so the return value is doing a little three-way thing and you need to know all three, iykyk:

  • < 0 β€” on error. it went wrong. 😭
  • 0 β€” if the last element was identified. we're done here, periodt. βœ…
  • id offset to next element β€” otherwise, this is your little breadcrumb to the next element. keep going bestie. 🫢

🧚 SEE ALSO 🧚

go read these, they're all lowkey connected and honestly kind of a friend group:


ngl bestie, if you're touching the restore path, you're gonna want the whole little squad above. read them together, it hits different. πŸ“

and that's the page!! πŸŽ€ this one lives in ./arch/arm64/kvm/vgic, dated October 2026 β€” screenshot it, cite it, frame it, slay. πŸ’…βœ¨

πŸ“¦ where this page comes from