pt_check_range(9)

💅 pt_check_range(9) — the kernel API manual, but make it cute

okay so bestie, welcome to pt_check_range from the Kernel API Manual — this is the little vibe-check function that makes sure a range is actually, y'know, iterable. no cap, it's giving gatekeeper but in a helpful way 🫶

---

✨ NAME ✨

pt_check_range — validates that the range can be iterated. literally its whole job. iconic behavior honestly 👑

---

🌸 SYNOPSIS 🌸

int pt_check_range (struct pt_range *range );

---

🎀 ARGUMENTS 🎀

• range — the range we're validating, bestie. that's the one. the range in question. 🦋

---

💖 DESCRIPTION 💖

so what it does is: it checks that VA and last_va both fall within the permitted range of VAs. like, are you supposed to be here, girl? 👀

and if the format is using PT_FEAT_SIGN_EXTEND, then it also checks that the sign extension is correct. double duty, highkey obsessed with how thorough it is ✨

fr fr, this is the function that goes "mhm mhm, and the sign extension? correct? slay." 💅

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/iommu/generic_pt/pt_iter.h
• pt_index_to_va(9)
• pt_entry_fully_covered(9)
• pt_range_to_index(9)
• pt_range_to_end_index(9)
• pt_next_entry(9)
• for_each_pt_level_entry(9)
• pt_load_single_entry(9)
• pt_top_range(9)
• pt_all_range(9)
• pt_upper_range(9)
• pt_make_range(9)
• pt_init(9)
• pt_init_top(9)
• pt_descend(9)
• pt_walk_range(9)
• pt_range_slice(9)
• pt_top_memsize_lg2(9)
• pt_compute_best_pgsize(9)
• PT_MAKE_LEVELS(9)

---

and that's the whole page, bestie — the squad over at ./drivers/iommu/generic_pt dropped this in October 2026, and it's still filed under pt_check_range(9) if you ever need to find it again. go off, range validator 🔥👑💜