pt_attr_from_entry(9)

✨ NAME ✨

okay bestie, this is pt_attr_from_entry(9) from the Kernel API Manual, and it is literally the “convert the permission bits back to attrs” girlie. 💅 No cap: pt_attr_from_entry converts the permission bits back to attrs. The way that's such a useful little glow-up. 🦋

🎀 SYNOPSIS 🎀

       void pt_attr_from_entry (const struct pt_state *pts , struct
       pt_write_attrs *attrs );

💖 ARGUMENTS 💖

• pts — entry to convert from. That's the thing you're reading, bestie. ✨
• attrs — resulting attrs. This is where the resulting attrs land. 🫶

🌸 DESCRIPTION 🌸

Fill in the attrs with the permission bits encoded in the current leaf entry. 💖 The attrs should be usable with pt_install_leaf_entry to reconstruct the same entry. So yes: permission bits in, attrs out, and pt_install_leaf_entry can use them to rebuild the same entry. That's the whole arc, and it ate. ✨

🔥 SEE ALSO 🔥

Kernel file: ./drivers/iommu/generic_pt/pt_common.h — the whole friend group:

• 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_full_va_prefix(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)

xoxo, your kernel bestie 💖 — from ./drivers/iommu/generic_pt, dated October 2026, for pt_attr_from_entry(9). 🎀