pt_entry_is_write_dirty(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pt_entry_is_write_dirty β€” the Kernel API Manual page you didn't know you needed

okay so bestie, we're in the Kernel API Manual today and this one's a little function with a big job: pt_entry_is_write_dirty.

✨ NAME ✨

pt_entry_is_write_dirty β€” true if the entry has been written to. that's it. that's the whole vibe check. 🫢

✨ SYNOPSIS ✨

bool pt_entry_is_write_dirty (const struct pt_state *pts );

✨ ARGUMENTS ✨

  • pts β€” the entry to query πŸŽ€ like, this is the thing you're asking about. the main character of the query, if you will.

✨ DESCRIPTION ✨

okay so what does "write dirty" even mean. ngl it sounds like a stan twitter subtweet but it's actually very literal: it means the HW has written to the OA translated by this entry. hardware did a little scribble. it's dirty now. periodt. πŸ’…

and here's the sneaky part β€” if the entry is contiguous, then you can't just check one thing and call it a day. you have to return the consolidated "write dirty" for all the items. all of them. fr fr, no skipping. πŸ‘‘

✨ SEE ALSO ✨

go off, read these too:


πŸ¦‹ okay that's the whole page, hope it slayed. this lil baddie lives in ./drivers/iommu/generic_pt, it's dated October 2026, and it's serving pt_entry_is_write_dirty(9) energy from the Kernel API Manual. mwah πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from