From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Maciej S. Szmigiero" Date: Tue, 09 Nov 2021 00:40:57 +0000 Subject: Re: [PATCH v5.5 16/30] KVM: x86: Don't assume old/new memslots are non-NULL at memslot commit Message-Id: <623f2d6e-6f75-03a9-2932-61190eebd30a@oracle.com> List-Id: References: <20211104002531.1176691-1-seanjc@google.com> <20211104002531.1176691-17-seanjc@google.com> In-Reply-To: <20211104002531.1176691-17-seanjc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Sean Christopherson Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , Atish Patra , David Hildenbrand , Cornelia Huck , Claudio Imbrenda , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Ben Gardon , Marc Zyngier , Huacai Chen , Aleksandar Markovic , Paul Mackerras , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank , Paolo Bonzini 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 Reviewed-by: Maciej S. Szmigiero