Re: [PATCH v6 08/25] KVM: arm64: iommu: Shadow host stage-2 page table

Mostafa Saleh
2026-05-04T12:29:09Z

On Fri, May 01, 2026 at 10:00:06AM -0300, Jason Gunthorpe wrote:
> On Fri, May 01, 2026 at 11:19:10AM +0000, Mostafa Saleh wrote:
> > Create a page-table for the IOMMU that shadows the host CPU stage-2
> > to establish DMA isolation.
>
> Is there a reason you can't just use the CPU S2 for the iommu?
>
> ie the CCA RMM is doing that, it is how ARM imagined this stuff would
> work.
>
> Once you start supporting DMA like this you have no choice but to keep
> a fully populated at all times S2 around, why not use that for the CPU
> too to avoid faults?
>
> I guess there is a reason, but maybe explain in the commit message?
>
> It sure would be simpler, you wouldn't have to mess with iopgtable at
> all...

Sharing the page table is tricky, this is something I have been thinking
about and my plan was to work on it after this series as it has some
constraints and would require core KVM changes.

So far this is the list of requirements/changes needed share the
stage-2 page table (besides the obvious: same page table format,
granularity, endianness...)

1) HW BBM is not supported in the hypervisor page table, that’s
because it can generate TLB conflict aborts, which the hypervisor
can not handle because of the limited syndrome information.
We can rely on FEAT_BBML3 which was newly introduced to work
around that, it’s quite niche and not supported in KVM yet or
have an allow list similar to the kernel
(as in cpu_supports_bbml2_noabort()) which also limits the number
of CPUs that can run this.

2) Handling page faults, devices must be able to stall and let the
hypervisor handle the page fault (which has to proxy through the
kernel as the hypervisor doesn’t handle interrupts), this includes
also IO page faults which are hard to get right from the HW which
and may lead to system stability issues or lockups.
Alternatively, we can pin the stage-2 pages, that would require some
hypercalls, hacks to the driver/IOMMU API and possibly new semantics
in the DMA-API for IDENTITY devices as they will still need to pin
the pages as they are actually in stage-2 translation and not bypass.

3) SMMUv3 must be coherent.

4) Support BTM/DVM for TLB invalidation, otherwise some hooks are
still required (although not io-pgtable-arm)

This is not the complete list, I am sure I will run into more issues
when prototyping this.

IMO, 1, 2 are the most tricky parts. It's more work and runs on very
limited systems, However, it can be implemented as an optimization)
which is my plan.

I am not sure how CCA deals with that, I’d expect they have a lot of
constraints on CPUs/SMMUs and DMA capable devices on those systems.

Thanks,
Mostafa

>
> Jason