pt_full_va_prefix(9)

💅 pt_full_va_prefix — the top bits of the VA ✨

okay so bestie, we're in the kernel API manual for pt_full_va_prefix(9) — yes that's a function name, yes it's a mouthful, no we're not renaming it 🫶

---

🌸 SYNOPSIS 🌸

pt_vaddr_t pt_full_va_prefix (const struct pt_common *common );

that's the whole vibe. one argument. one return. slay.

---

💖 ARGUMENTS 💖

• common — the page table you're querying, bestie. that's it, that's the input 🎀

---

✨ DESCRIPTION ✨

okay so here's the tea ☕ — this value is usually 0. like, normally, that's just the answer, no drama.

but 💀 some formats have their VA space going downward from PT_VADDR_MAX, and for those, this function returns that instead. so not zero. a whole different vibe.

and here's the part you cannot skip, i'm serious, highkey important 👑 — this value must always be adjusted by struct pt_common max_vasz_lg2. always. every time. no cap. don't just grab the return value and run off into the sunset 🏃‍♀️💨

---

🦋 SEE ALSO 🦋

the kernel file itself, in all its glory:

• ./drivers/iommu/generic_pt/pt_common.h

and the whole friend group 🫶 (go say hi to all of them):

• pt_attr_from_entry(9)
• pt_can_have_leaf(9)
• pt_can_have_table(9)
• pt_clear_entries(9)
• pt_entry_make_write_dirty(9)
• pt_entry_make_write_clean(9)
• pt_entry_is_write_dirty(9)
• pt_dirty_supported(9)
• pt_entry_num_contig_lg2(9)
• pt_entry_oa(9)
• pt_entry_oa_lg2sz(9)
• pt_entry_oa_exact(9)
• pt_has_system_page_size(9)
• pt_install_leaf_entry(9)
• pt_install_table(9)
• pt_item_oa(9)
• pt_load_entry_raw(9)
• pt_max_oa_lg2(9)
• pt_num_items_lg2(9)
• pt_pgsz_lg2_to_level(9)
• pt_possible_sizes(9)
• pt_table_item_lg2sz(9)
• pt_table_oa_lg2sz(9)
• pt_table_pa(9)
• pt_table_ptr(9)
• pt_max_sw_bit(9)
• pt_test_sw_bit_acquire(9)
• pt_set_sw_bit_release(9)
• pt_load_entry(9)

---

and that's the whole page, bestie 💜 go read a page table, you got this 🌈⭐

source: ./drivers/iommu/generic_pt — dated October 2026, manual section pt_full_va_prefix(9) 🎀 ok bye ily 🫶