Re: [PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit
"Maciej S. Szmigiero" <[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 | <[email protected]> |
On 04.11.2021 01:25, Sean Christopherson wrote: > Play nice with a NULL @old or @new when handling memslot updates so that > common KVM can pass NULL for one or the other in CREATE and DELETE cases > instead of having to synthesize a dummy memslot. > > No functional change intended. > > Signed-off-by: Sean Christopherson <[email protected]> Reviewed-by: Maciej S. Szmigiero <[email protected]>