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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit
From: "Maciej S. Szmigiero" <maciej.szmigiero@xxxxxxxxxx>
Date: Tue, 9 Nov 2021 01:40:57 +0100
Cc: James Morse <james.morse@xxxxxxx>, Alexandru Elisei <alexandru.elisei@xxxxxxx>, Suzuki K Poulose <suzuki.poulose@xxxxxxx>, Atish Patra <atish.patra@xxxxxxx>, David Hildenbrand <david@xxxxxxxxxx>, Cornelia Huck <cohuck@xxxxxxxxxx>, Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx>, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>, Wanpeng Li <wanpengli@xxxxxxxxxxx>, Jim Mattson <jmattson@xxxxxxxxxx>, Joerg Roedel <joro@xxxxxxxxxx>, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, kvmarm@xxxxxxxxxxxxxxxxxxxxx, linux-mips@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, kvm-ppc@xxxxxxxxxxxxxxx, kvm-riscv@xxxxxxxxxxxxxxxxxxx, linux-riscv@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Ben Gardon <bgardon@xxxxxxxxxx>, Marc Zyngier <maz@xxxxxxxxxx>, Huacai Chen <chenhuacai@xxxxxxxxxx>, Aleksandar Markovic <aleksandar.qemu.devel@xxxxxxxxx>, Paul Mackerras <paulus@xxxxxxxxxx>, Anup Patel <anup.patel@xxxxxxx>, Paul Walmsley <paul.walmsley@xxxxxxxxxx>, Palmer Dabbelt <palmer@xxxxxxxxxxx>, Albert Ou <aou@xxxxxxxxxxxxxxxxx>, Christian Borntraeger <borntraeger@xxxxxxxxxx>, Janosch Frank <frankja@xxxxxxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>
In-reply-to: <20211104002531.1176691-17-seanjc@google.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0

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@xxxxxxxxxx>


Reviewed-by: Maciej S. Szmigiero <maciej.szmigiero@xxxxxxxxxx>

References:
- [PATCH v5.5 00/30] KVM: Scalable memslots implementation
  - From: Sean Christopherson
- [PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit
  - From: Sean Christopherson

Prev by Date: Re: [PATCH v5.5 15/30] KVM: Use prepare/commit hooks to handle generic memslot metadata updates
Next by Date: Re: [PATCH v5.5 18/30] KVM: Don't make a full copy of the old memslot in __kvm_set_memory_region()
Previous by thread: [PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit
Next by thread: [PATCH v5.5 17/30] KVM: s390: Skip gfn/size sanity checks on memslot DELETE or FLAGS_ONLY
Index(es):
- Date
- Thread

[Index of Archives] [KVM Development] [KVM ARM] [KVM ia64] [Linux Virtualization] [Linux USB Devel] [Linux Video] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [Big List of Linux Books]