diff for duplicates of <20200207220325.GO2401@linux.intel.com> diff --git a/a/1.txt b/N1/1.txt index 2b187de..6217f9f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -18,7 +18,7 @@ On Fri, Feb 07, 2020 at 04:46:23PM -0500, Peter Xu wrote: > > > > > Is this intended? > > > > > > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely -> > > > uncommon, but possible. Therefore "hva = 0" shouldn't be used to +> > > > uncommon, but possible. Therefore "hva == 0" shouldn't be used to > > > > indicate an invalid slot. > > > > > > Note that this is the deletion path in __x86_set_memory_region() not @@ -41,3 +41,7 @@ On Fri, Feb 07, 2020 at 04:46:23PM -0500, Peter Xu wrote: I'm not arguing that's not the case. My point is that there's nothing special about '0', so why use it? E.g. "hva = 1" would also be ok from a functional perspective, but more obviously "wrong". +_______________________________________________ +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 1e78db6..b27a847 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -7,29 +7,25 @@ "ref\020200207214623.GF720553@xz-x1\0" "From\0Sean Christopherson <sean.j.christopherson@intel.com>\0" "Subject\0Re: [PATCH v5 17/19] KVM: Terminate memslot walks via used_slots\0" - "Date\0Fri, 07 Feb 2020 22:03:25 +0000\0" + "Date\0Fri, 7 Feb 2020 14:03:25 -0800\0" "To\0Peter Xu <peterx@redhat.com>\0" - "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + "Cc\0Wanpeng Li <wanpengli@tencent.com>" + kvm@vger.kernel.org + David Hildenbrand <david@redhat.com> + linux-mips@vger.kernel.org Paul Mackerras <paulus@ozlabs.org> - Christian Borntraeger <borntraeger@de.ibm.com> + kvmarm@lists.cs.columbia.edu Janosch Frank <frankja@linux.ibm.com> - David Hildenbrand <david@redhat.com> - Cornelia Huck <cohuck@redhat.com> - Vitaly Kuznetsov <vkuznets@redhat.com> - Wanpeng Li <wanpengli@tencent.com> - Jim Mattson <jmattson@google.com> - Joerg Roedel <joro@8bytes.org> Marc Zyngier <maz@kernel.org> - James Morse <james.morse@arm.com> - Julien Thierry <julien.thierry.kdev@gmail.com> - Suzuki K Poulose <suzuki.poulose@arm.com> - linux-mips@vger.kernel.org - kvm@vger.kernel.org + Joerg Roedel <joro@8bytes.org> + Christian Borntraeger <borntraeger@de.ibm.com> kvm-ppc@vger.kernel.org linux-arm-kernel@lists.infradead.org - kvmarm@lists.cs.columbia.edu + Jim Mattson <jmattson@google.com> + Cornelia Huck <cohuck@redhat.com> linux-kernel@vger.kernel.org - Christoffer Dall <christoffer.dall@arm.com> + Paolo Bonzini <pbonzini@redhat.com> + Vitaly Kuznetsov <vkuznets@redhat.com> " Philippe Mathieu-Daud\303\251 <f4bug@amsat.org>\0" "\00:1\0" "b\0" @@ -53,7 +49,7 @@ "> > > > > Is this intended?\n" "> > > > \n" "> > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely\n" - "> > > > uncommon, but possible. Therefore \"hva = 0\" shouldn't be used to\n" + "> > > > uncommon, but possible. Therefore \"hva == 0\" shouldn't be used to\n" "> > > > indicate an invalid slot.\n" "> > > \n" "> > > Note that this is the deletion path in __x86_set_memory_region() not\n" @@ -75,6 +71,10 @@ "\n" "I'm not arguing that's not the case. My point is that there's nothing\n" "special about '0', so why use it? E.g. \"hva = 1\" would also be ok from a\n" - "functional perspective, but more obviously \"wrong\"." + "functional perspective, but more obviously \"wrong\".\n" + "_______________________________________________\n" + "kvmarm mailing list\n" + "kvmarm@lists.cs.columbia.edu\n" + https://lists.cs.columbia.edu/mailman/listinfo/kvmarm -d8f443425547617a9dfd47ba3fb1ecf253d0a7bc5e63a84b9db2ff508570745f +236af2c1a1aab027f0f6df82785210ad63c8bffe761a2704cb16aea87eb561a4
diff --git a/a/1.txt b/N2/1.txt index 2b187de..0bca080 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -18,7 +18,7 @@ On Fri, Feb 07, 2020 at 04:46:23PM -0500, Peter Xu wrote: > > > > > Is this intended? > > > > > > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely -> > > > uncommon, but possible. Therefore "hva = 0" shouldn't be used to +> > > > uncommon, but possible. Therefore "hva == 0" shouldn't be used to > > > > indicate an invalid slot. > > > > > > Note that this is the deletion path in __x86_set_memory_region() not diff --git a/a/content_digest b/N2/content_digest index 1e78db6..74b129c 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -7,7 +7,7 @@ "ref\020200207214623.GF720553@xz-x1\0" "From\0Sean Christopherson <sean.j.christopherson@intel.com>\0" "Subject\0Re: [PATCH v5 17/19] KVM: Terminate memslot walks via used_slots\0" - "Date\0Fri, 07 Feb 2020 22:03:25 +0000\0" + "Date\0Fri, 7 Feb 2020 14:03:25 -0800\0" "To\0Peter Xu <peterx@redhat.com>\0" "Cc\0Paolo Bonzini <pbonzini@redhat.com>" Paul Mackerras <paulus@ozlabs.org> @@ -53,7 +53,7 @@ "> > > > > Is this intended?\n" "> > > > \n" "> > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely\n" - "> > > > uncommon, but possible. Therefore \"hva = 0\" shouldn't be used to\n" + "> > > > uncommon, but possible. Therefore \"hva == 0\" shouldn't be used to\n" "> > > > indicate an invalid slot.\n" "> > > \n" "> > > Note that this is the deletion path in __x86_set_memory_region() not\n" @@ -77,4 +77,4 @@ "special about '0', so why use it? E.g. \"hva = 1\" would also be ok from a\n" "functional perspective, but more obviously \"wrong\"." -d8f443425547617a9dfd47ba3fb1ecf253d0a7bc5e63a84b9db2ff508570745f +d3763c461516cc60a5a597a8cca2abd06ce37fa97f5ac2cc3fbd194164bfa78f
diff --git a/a/1.txt b/N3/1.txt index 2b187de..e198482 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -18,7 +18,7 @@ On Fri, Feb 07, 2020 at 04:46:23PM -0500, Peter Xu wrote: > > > > > Is this intended? > > > > > > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely -> > > > uncommon, but possible. Therefore "hva = 0" shouldn't be used to +> > > > uncommon, but possible. Therefore "hva == 0" shouldn't be used to > > > > indicate an invalid slot. > > > > > > Note that this is the deletion path in __x86_set_memory_region() not @@ -41,3 +41,8 @@ On Fri, Feb 07, 2020 at 04:46:23PM -0500, Peter Xu wrote: I'm not arguing that's not the case. My point is that there's nothing special about '0', so why use it? E.g. "hva = 1" would also be ok from a functional perspective, but more obviously "wrong". + +_______________________________________________ +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 1e78db6..bda6a59 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -7,29 +7,29 @@ "ref\020200207214623.GF720553@xz-x1\0" "From\0Sean Christopherson <sean.j.christopherson@intel.com>\0" "Subject\0Re: [PATCH v5 17/19] KVM: Terminate memslot walks via used_slots\0" - "Date\0Fri, 07 Feb 2020 22:03:25 +0000\0" + "Date\0Fri, 7 Feb 2020 14:03:25 -0800\0" "To\0Peter Xu <peterx@redhat.com>\0" - "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + "Cc\0Wanpeng Li <wanpengli@tencent.com>" + kvm@vger.kernel.org + David Hildenbrand <david@redhat.com> + linux-mips@vger.kernel.org Paul Mackerras <paulus@ozlabs.org> - Christian Borntraeger <borntraeger@de.ibm.com> + kvmarm@lists.cs.columbia.edu Janosch Frank <frankja@linux.ibm.com> - David Hildenbrand <david@redhat.com> - Cornelia Huck <cohuck@redhat.com> - Vitaly Kuznetsov <vkuznets@redhat.com> - Wanpeng Li <wanpengli@tencent.com> - Jim Mattson <jmattson@google.com> - Joerg Roedel <joro@8bytes.org> Marc Zyngier <maz@kernel.org> - James Morse <james.morse@arm.com> + Joerg Roedel <joro@8bytes.org> + Christian Borntraeger <borntraeger@de.ibm.com> Julien Thierry <julien.thierry.kdev@gmail.com> Suzuki K Poulose <suzuki.poulose@arm.com> - linux-mips@vger.kernel.org - kvm@vger.kernel.org kvm-ppc@vger.kernel.org linux-arm-kernel@lists.infradead.org - kvmarm@lists.cs.columbia.edu - linux-kernel@vger.kernel.org + Jim Mattson <jmattson@google.com> + Cornelia Huck <cohuck@redhat.com> Christoffer Dall <christoffer.dall@arm.com> + linux-kernel@vger.kernel.org + James Morse <james.morse@arm.com> + Paolo Bonzini <pbonzini@redhat.com> + Vitaly Kuznetsov <vkuznets@redhat.com> " Philippe Mathieu-Daud\303\251 <f4bug@amsat.org>\0" "\00:1\0" "b\0" @@ -53,7 +53,7 @@ "> > > > > Is this intended?\n" "> > > > \n" "> > > > Yes. It's possible to allow VA=0 for userspace mappings. It's extremely\n" - "> > > > uncommon, but possible. Therefore \"hva = 0\" shouldn't be used to\n" + "> > > > uncommon, but possible. Therefore \"hva == 0\" shouldn't be used to\n" "> > > > indicate an invalid slot.\n" "> > > \n" "> > > Note that this is the deletion path in __x86_set_memory_region() not\n" @@ -75,6 +75,11 @@ "\n" "I'm not arguing that's not the case. My point is that there's nothing\n" "special about '0', so why use it? E.g. \"hva = 1\" would also be ok from a\n" - "functional perspective, but more obviously \"wrong\"." + "functional perspective, but more obviously \"wrong\".\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 -d8f443425547617a9dfd47ba3fb1ecf253d0a7bc5e63a84b9db2ff508570745f +26f7bc6ec1e74c0c62b31bc3bf81aa343041dc0e26be7dd018396f43fff70e91
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.