pt_all_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pt_all_range(9) πŸ’…

okay so bestie, welcome to the pt_all_range manpage from the Kernel API Manual β€” yes, the whole manual, we're doing this 🫢


✨ NAME ✨

pt_all_range β€” returns a range that spans the entire page table, no cap πŸ‘‘


🌸 SYNOPSIS 🌸

struct pt_range pt_all_range (struct pt_common *common );

πŸŽ€ ARGUMENTS πŸŽ€

  • common β€” the table. that's it. that's the whole argument. she's lowkey a one-parameter icon πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

so the range you get back spans the whole page table β€” like, all of it, every last crumb, main character energy πŸ“.

but bestie, listen to me, this part is important: because of how PT_FEAT_SIGN_EXTEND is supported, range->va and range->last_va will be incorrect during the iteration. as in, do not touch them. do not look at them. do not pass go. πŸ™ˆ

fr fr, they "must not be accessed" β€” that's not a vibe suggestion, that's the rule. if you read them mid-iteration you're on your own 😭

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/iommu/generic_pt/pt_iter.h β€” go read her, she knows things πŸ’œ

the whole squad, in order:


okay that's the whole page, you ate that πŸ’…βœ¨ this came to you courtesy of ./drivers/iommu/generic_pt, dated October 2026 β€” mwah, stan, periodt πŸŽ€πŸ’–

πŸ“¦ where this page comes from