pvr_page_ta...ntry_raw_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to pvr_page_table_l0_entry_raw_set(9) from the Kernel API Manual β€” yes, we are deep in the raw-level-0-page-table-entry trenches and it's lowkey iconic. πŸ’…βœ¨

🌸 NAME 🌸

pvr_page_table_l0_entry_raw_set β€” write a valid entry into a raw level 0 page table. That's the whole assignment, no cap. 🫢

✨ SYNOPSIS ✨

void pvr_page_table_l0_entry_raw_set (struct pvr_page_table_l0_entry_raw
       *entry , dma_addr_t dma_addr , struct pvr_page_flags_raw flags );

that's the signature, bestie β€” copy it exactly, character for character. πŸŽ€

πŸŽ€ ARGUMENTS πŸŽ€

  • entry β€” target raw level 0 page table entry. This is the spot getting written, main character energy.
  • dma_addr β€” DMA address of the physical page to be associated with entry. It's the address that gets linked up with the entry.
  • flags β€” options to be set on entry. Cute little options, but read the description before you go feral. 😌

πŸ¦‹ DESCRIPTION πŸ¦‹

When calling this function, child_table_dma_addr must be a valid DMA address and a multiple of PVR_DEVICE_PAGE_SIZE.

and yes, the page literally says child_table_dma_addr right there, even though the argument is called dma_addr β€” just keeping the original wording 100% intact. πŸ™ˆ

The flags parameter is directly assigned into entry. It is the caller's responsibility to ensure that only bits specified in struct pvr_page_flags_raw are set in flags. So like, don't sneak extra bits in there β€” that's on you, bestie. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group is huge, but every single one is here, zero skips:


mwah πŸ’‹ β€” source/version: ./drivers/gpu/drm/imagination; date: October 2026; footer page label: pvr_page_ta...ntry_raw_set(9). That's the whole page, bestie. Go write that raw level 0 entry and slay. πŸŽ€βœ¨

πŸ“¦ where this page comes from