pvr_mmu_op_c...xt_next_page(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this page lives in the Kernel API Manual β€” the header shortens the whole thing to pvr_mmu_op_c...xt_next_page(9), iykyk β€” and the main character is:

pvr_mmu_op_context_next_page β€” Advance the current page of an MMU op context. πŸ’…βœ¨

🌸 SYNOPSIS 🌸

int pvr_mmu_op_context_next_page (struct pvr_mmu_op_context *op_ctx , bool should_create );

πŸŽ€ ARGUMENTS πŸŽ€

  • op_ctx β€” Target MMU op context. That's the target vibe right there. 🫢
  • should_create β€” Specify whether new page tables should be created when empty page table entries are encountered during traversal. So basically: new tables or not? πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so if should_create is false, it is the caller's responsibility to verify that the state of the table references in op_ctx is valid on return. no cap. If -ENXIO is returned, at least one of the table references is invalid. It should be noted that op_ctx as a whole will be left in a valid state if -ENXIO is returned, unlike other error codes. The caller should check which references are invalid by comparing them to NULL. Only &ptr->l2_table is guaranteed to be valid, since it represents the root of the page table tree structure. 🌈✨

⭐ RETURN ⭐

  • 0 on success, slay. βœ…
  • -EPERM if the operation would wrap at the top of the page table hierarchy. πŸŒ€
  • -ENXIO if should_create is false and a page table of any level would have otherwise been created. 🚫
  • Any error returned while attempting to create missing page tables if should_create is true. 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/gpu/drm/imagination/pvr_mmu.c β€” yes bestie, that's the source file. And then the whole friend group:


before you close the tab, bestie: this page's footer info is source ./drivers/gpu/drm/imagination, date October 2026, and page tag pvr_mmu_op_c...xt_next_page(9). that's the whole sign-off, now wrapped in a bow πŸŽ€πŸ’–

πŸ“¦ where this page comes from