Re: [PATCH v5.5 08/30] KVM: arm64: Use "new" memslot instead of userspace memory region
Reiji Watanabe <[email protected]>
| Newsgroups | org.kernel.vger.kvm-ppc,dev.linux.lists.kvmarm,org.infradead.lists.kvm-riscv,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips |
|---|---|
| Message-ID | <CAAeT=FxcFq2SoM5xRYJfB=bBzGrY1uuEUhvFd+6sb86y-rg_Yw@mail.gmail.com> |
On Wed, Nov 3, 2021 at 5:26 PM Sean Christopherson <[email protected]> wrote: > > Get the slot ID, hva, etc... from the "new" memslot instead of the > userspace memory region when preparing/committing a memory region. This > will allow a future commit to drop @mem from the prepare/commit hooks > once all architectures convert to using "new". > > Opportunistically wait to get the hva begin+end until after filtering out > the DELETE case in anticipation of a future commit passing NULL for @new > when deleting a memslot. > > Signed-off-by: Sean Christopherson <[email protected]> Reviewed-by: Reiji Watanabe <[email protected]>