diff for duplicates of <YGTYf9sWVIJqqswq@google.com> diff --git a/a/1.txt b/N1/1.txt index 4aaea89..01e0dce 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -26,6 +26,10 @@ On Wed, Mar 31, 2021, Paolo Bonzini wrote: > */ An alternative would be to not take the lock in install_new_memslots() if -kvm->users_count = 0. It'd be weirder to document, and the conditional locking +kvm->users_count == 0. It'd be weirder to document, and the conditional locking would still be quite ugly. Not sure if that's better than blasting a lock during destruction? +_______________________________________________ +kvmarm mailing list +kvmarm@lists.cs.columbia.edu +https://lists.cs.columbia.edu/mailman/listinfo/kvmarm diff --git a/a/content_digest b/N1/content_digest index 3bfd5ec..9e561d0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,24 +5,21 @@ "Subject\0Re: [PATCH 16/18] KVM: Don't take mmu_lock for range invalidation unless necessary\0" "Date\0Wed, 31 Mar 2021 20:15:59 +0000\0" "To\0Paolo Bonzini <pbonzini@redhat.com>\0" - "Cc\0Marc Zyngier <maz@kernel.org>" - Huacai Chen <chenhuacai@kernel.org> - Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> - Paul Mackerras <paulus@ozlabs.org> - James Morse <james.morse@arm.com> - Julien Thierry <julien.thierry.kdev@gmail.com> - Suzuki K Poulose <suzuki.poulose@arm.com> - Vitaly Kuznetsov <vkuznets@redhat.com> - Wanpeng Li <wanpengli@tencent.com> - Jim Mattson <jmattson@google.com> + "Cc\0Wanpeng Li <wanpengli@tencent.com>" + kvm@vger.kernel.org + Marc Zyngier <maz@kernel.org> Joerg Roedel <joro@8bytes.org> - linux-arm-kernel@lists.infradead.org - kvmarm@lists.cs.columbia.edu + Huacai Chen <chenhuacai@kernel.org> linux-mips@vger.kernel.org - kvm@vger.kernel.org kvm-ppc@vger.kernel.org linux-kernel@vger.kernel.org - " Ben Gardon <bgardon@google.com>\0" + Paul Mackerras <paulus@ozlabs.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + linux-arm-kernel@lists.infradead.org + Ben Gardon <bgardon@google.com> + Vitaly Kuznetsov <vkuznets@redhat.com> + kvmarm@lists.cs.columbia.edu + " Jim Mattson <jmattson@google.com>\0" "\00:1\0" "b\0" "On Wed, Mar 31, 2021, Paolo Bonzini wrote:\n" @@ -53,8 +50,12 @@ "> \t */\n" "\n" "An alternative would be to not take the lock in install_new_memslots() if\n" - "kvm->users_count = 0. It'd be weirder to document, and the conditional locking\n" + "kvm->users_count == 0. It'd be weirder to document, and the conditional locking\n" "would still be quite ugly. Not sure if that's better than blasting a lock\n" - during destruction? + "during destruction?\n" + "_______________________________________________\n" + "kvmarm mailing list\n" + "kvmarm@lists.cs.columbia.edu\n" + https://lists.cs.columbia.edu/mailman/listinfo/kvmarm -e5fc6e4ffefa1fcc778980586aeddb1271ea67acc0e7ad2f1cc4f928d4488fee +7f18509afd54b4e43f31b2a8e37182e543a11b5878766bd5559fc5fcb37fd82b
diff --git a/a/1.txt b/N2/1.txt index 4aaea89..71e7377 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -26,6 +26,6 @@ On Wed, Mar 31, 2021, Paolo Bonzini wrote: > */ An alternative would be to not take the lock in install_new_memslots() if -kvm->users_count = 0. It'd be weirder to document, and the conditional locking +kvm->users_count == 0. It'd be weirder to document, and the conditional locking would still be quite ugly. Not sure if that's better than blasting a lock during destruction? diff --git a/a/content_digest b/N2/content_digest index 3bfd5ec..3735ff1 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -53,8 +53,8 @@ "> \t */\n" "\n" "An alternative would be to not take the lock in install_new_memslots() if\n" - "kvm->users_count = 0. It'd be weirder to document, and the conditional locking\n" + "kvm->users_count == 0. It'd be weirder to document, and the conditional locking\n" "would still be quite ugly. Not sure if that's better than blasting a lock\n" during destruction? -e5fc6e4ffefa1fcc778980586aeddb1271ea67acc0e7ad2f1cc4f928d4488fee +59f5b768165761db9f512ca36788b9dc7cb0d56f0d7fae5ed37209f3b7123b03
diff --git a/a/1.txt b/N3/1.txt index 4aaea89..f19049f 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -26,6 +26,11 @@ On Wed, Mar 31, 2021, Paolo Bonzini wrote: > */ An alternative would be to not take the lock in install_new_memslots() if -kvm->users_count = 0. It'd be weirder to document, and the conditional locking +kvm->users_count == 0. It'd be weirder to document, and the conditional locking would still be quite ugly. Not sure if that's better than blasting a lock during destruction? + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N3/content_digest index 3bfd5ec..94f5f6e 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -53,8 +53,13 @@ "> \t */\n" "\n" "An alternative would be to not take the lock in install_new_memslots() if\n" - "kvm->users_count = 0. It'd be weirder to document, and the conditional locking\n" + "kvm->users_count == 0. It'd be weirder to document, and the conditional locking\n" "would still be quite ugly. Not sure if that's better than blasting a lock\n" - during destruction? + "during destruction?\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -e5fc6e4ffefa1fcc778980586aeddb1271ea67acc0e7ad2f1cc4f928d4488fee +0bfe6d74cc5b6c7c4b7a57dd4252923c60b6bb9b9d4b77873fe3d85a24482f31
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.