Re: [PATCH 1/2] KVM: arm64: nv: Allocate the shadow S2 MMUs individually
Karl Mehltretter <[email protected]> Tue, 4 Aug 2026 23:54:30 +0200
| Newsgroups | gmane.linux.kernel.stable,gmane.linux.ports.arm.kernel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Aug 04, 2026 at 03:56:47PM +0100, Marc Zyngier wrote: > > The other thing is that reallocating the pointer array isn't great. It > > adds complexity, and makes everything more fragile than it should be. > > > > See the hack below that seems to work OK. > > Your draft is indeed a bit simpler. Should I send a cleaned-up version as v2? I would allocate the table on the first call to kvm_vcpu_init_nested() and not in kvm_init_nested(), so it cannot leak if VM creation fails. There's another issue in the current code: the ptdump debugfs file keeps the raw mmu pointer as its private data. I would add that to the commit message. Thanks, Karl