iopgtable_lookup_entry(9)
π iopgtable_lookup_entry(9) β a Kernel API Manual moment π
okay bestie so this is iopgtable_lookup_entry π β it lives in the kernel API manual (section 9, iykyk) and it's literally the page you read when you need to look up an iommu pte entry β¨
β¨ NAME β¨
iopgtable_lookup_entry β Lookup an iommu pte entry πΈ
π¦ SYNOPSIS π¦
void iopgtable_lookup_entry (struct omap_iommu *obj , u32 da , u32
**ppgd , u32 **ppte );
that's the whole vibe, no cap β it returns void, so don't go looking for a return value, there isn't one π
π ARGUMENTS π
objβ the target iommu π― like, the one you're messing withdaβ the iommu device virtual address π§ this is the address you're looking upppgdβ iommu pgd entry pointer to be returned π yes bestie, it comes back through this pointerppteβ iommu pte entry pointer to be returned π«Ά same deal, your pte entry lands here
π SEE ALSO π
the kernel file ./drivers/iommu/omap-iommu.c is where it all goes down, and it's giving main character energy π₯ β go read it alongside these iconic siblings:
to_omap_domain(9)omap_iommu_save_ctx(9)omap_iommu_restore_ctx(9)load_iotlb_entry(9)flush_iotlb_page(9)flush_iotlb_all(9)omap_iopgtable_store_entry(9)iopgtable_clear_entry(9)omap_iommu_attach(9)omap_iommu_detach(9)omap_iommu_domain_deactivate(9)omap_iommu_domain_activate(9)omap_iommu_runtime_suspend(9)omap_iommu_runtime_resume(9)omap_iommu_prepare(9)
all of them ate, fr fr π
that's the page diva π sourced from ./drivers/iommu, dated October 2026 β periodt, go look up that entry βπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms