pvr_mmu_op_c..._sync_manual(9)

📦 version 7.3.1, in nixpkgs unstable

💖 pvr_mmu_op_c..._sync_manual(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this one is pvr_mmu_op_c..._sync_manual(9), which is the long dramatic name for a function with a long dramatic job. she's basically the "go go go" button for page tables. let's get into it 🎀

✨ NAME ✨

pvr_mmu_op_context_sync_manual — triggers a sync of some or all of the page tables that a MMU op context is pointing at. like, "hey bestie, flush the vibes, some of them, or all of them, your call" 💅

🌸 SYNOPSIS 🌸

void pvr_mmu_op_context_sync_manual (struct pvr_mmu_op_context *op_ctx ,
enum pvr_mmu_sync_level level );

no return value, no cap, just vibes and side effects 🦋

🦋 ARGUMENTS 🦋

  • op_ctx — the target MMU op context. the main character of this whole operation 👑
  • level — the maximum page table level to sync. like a depth limit but for syncing ✨

💀 DESCRIPTION 💀

okay so this is the important part, listen up 🫶

do not call this function directly. i'm so serious. this is not a "just try it and see what happens" situation. instead you use pvr_mmu_op_context_sync_partial, which actually gets checked against the current value of op_ctx->sync_level_required — and that value is set by pvr_mmu_op_context_require_sync. so the whole safety-check pipeline exists and you're gonna respect it, periodt 🌈

literally do not call this directly, bestie. use pvr_mmu_op_context_sync_partial. the check is the whole point 💅

💜 SEE ALSO 💜

the whole extended friend group, iykyk:

that's the whole squad, no gatekeeping 💖 if you made it this far, you're literally a kernel girlie now. slay 🧚

<div align="center">— ✨ later, bestie ✨ —</div>

this page lives in ./drivers/gpu/drm/imagination (yes that's the source/version, october 2026 date energy 🍓) and it signs off as pvr_mmu_op_c..._sync_manual(9). bye bye, drink water, don't call this function directly 💜🦋🎀
📦 where this page comes from