[PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit

Maciej S. Szmigiero maciej.szmigiero at oracle.com
Mon Nov 8 16:40:57 PST 2021


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 <seanjc at google.com>

Reviewed-by: Maciej S. Szmigiero <maciej.szmigiero at oracle.com>



More information about the kvm-riscv mailing list