diff for duplicates of <ZXo3REB8g-ZecT2U@google.com> diff --git a/a/1.txt b/N1/1.txt index dd89691..6a754e6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Thu, Dec 14, 2023, Maxim Levitsky wrote: > On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote: > > On Sun, Dec 10, 2023, Jim Mattson wrote: -> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote: +> > > On Thu, Dec 7, 2023 at 8:21 AM Sean Christopherson <seanjc@google.com> wrote: > > > > Doh. We got the less obvious cases and missed the obvious one. > > > > > > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That diff --git a/a/content_digest b/N1/content_digest index 16a5c3a..80dc6c4 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,15 +5,39 @@ "ref\0ZXh8Nq_y_szj1WN0@google.com\0" "ref\05ca5592b21131f515e296afae006e5bb28b1fb87.camel@redhat.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" + "Subject\0Re: [PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" "Date\0Wed, 13 Dec 2023 14:59:16 -0800\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Maxim Levitsky <mlevitsk@redhat.com>\0" + "Cc\0Jim Mattson <jmattson@google.com>" + alexandru.elisei@arm.com + anup@brainfault.org + aou@eecs.berkeley.edu + atishp@atishpatra.org + borntraeger@linux.ibm.com + chenhuacai@kernel.org + david@redhat.com + frankja@linux.ibm.com + imbrenda@linux.ibm.com + james.morse@arm.com + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + linux-kernel@vger.kernel.org + linux-mips@vger.kernel.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + maz@kernel.org + oliver.upton@linux.dev + palmer@dabbelt.com + paul.walmsley@sifive.com + pbonzini@redhat.com + " suzuki.poulose@arm.com\0" "\00:1\0" "b\0" "On Thu, Dec 14, 2023, Maxim Levitsky wrote:\n" "> On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote:\n" "> > On Sun, Dec 10, 2023, Jim Mattson wrote:\n" - "> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote:\n" + "> > > On Thu, Dec 7, 2023 at 8:21\342\200\257AM Sean Christopherson <seanjc@google.com> wrote:\n" "> > > > Doh. We got the less obvious cases and missed the obvious one.\n" "> > > > \n" "> > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That\n" @@ -84,4 +108,4 @@ "nested virtualization awareness because the event itself is tracked for the vCPU\n" as a whole. -364b412e251e40594b2edb84d415468a2ae371edc91ba665cdbae8df24ecaa1d +381f40f9ede8f3b7807bfe3be6b8da651bfd8ffd97bce56aa3864eac46b21b7a
diff --git a/a/1.txt b/N2/1.txt index dd89691..16eb19e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,7 +1,7 @@ On Thu, Dec 14, 2023, Maxim Levitsky wrote: > On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote: > > On Sun, Dec 10, 2023, Jim Mattson wrote: -> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote: +> > > On Thu, Dec 7, 2023 at 8:21 AM Sean Christopherson <seanjc@google.com> wrote: > > > > Doh. We got the less obvious cases and missed the obvious one. > > > > > > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That @@ -71,3 +71,8 @@ to L2, e.g. nVMX's preemption timer, MTF, and pending virtual interrupts (hmm, I suspect nSVM's vNMI is broken too). Things like INIT and SMI don't require nested virtualization awareness because the event itself is tracked for the vCPU as a whole. + +_______________________________________________ +linux-riscv mailing list +linux-riscv@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-riscv diff --git a/a/content_digest b/N2/content_digest index 16a5c3a..6e22a82 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -5,15 +5,39 @@ "ref\0ZXh8Nq_y_szj1WN0@google.com\0" "ref\05ca5592b21131f515e296afae006e5bb28b1fb87.camel@redhat.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" + "Subject\0Re: [PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" "Date\0Wed, 13 Dec 2023 14:59:16 -0800\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Maxim Levitsky <mlevitsk@redhat.com>\0" + "Cc\0Jim Mattson <jmattson@google.com>" + alexandru.elisei@arm.com + anup@brainfault.org + aou@eecs.berkeley.edu + atishp@atishpatra.org + borntraeger@linux.ibm.com + chenhuacai@kernel.org + david@redhat.com + frankja@linux.ibm.com + imbrenda@linux.ibm.com + james.morse@arm.com + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + linux-kernel@vger.kernel.org + linux-mips@vger.kernel.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + maz@kernel.org + oliver.upton@linux.dev + palmer@dabbelt.com + paul.walmsley@sifive.com + pbonzini@redhat.com + " suzuki.poulose@arm.com\0" "\00:1\0" "b\0" "On Thu, Dec 14, 2023, Maxim Levitsky wrote:\n" "> On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote:\n" "> > On Sun, Dec 10, 2023, Jim Mattson wrote:\n" - "> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote:\n" + "> > > On Thu, Dec 7, 2023 at 8:21\342\200\257AM Sean Christopherson <seanjc@google.com> wrote:\n" "> > > > Doh. We got the less obvious cases and missed the obvious one.\n" "> > > > \n" "> > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That\n" @@ -82,6 +106,11 @@ "to L2, e.g. nVMX's preemption timer, MTF, and pending virtual interrupts (hmm,\n" "I suspect nSVM's vNMI is broken too). Things like INIT and SMI don't require\n" "nested virtualization awareness because the event itself is tracked for the vCPU\n" - as a whole. + "as a whole.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -364b412e251e40594b2edb84d415468a2ae371edc91ba665cdbae8df24ecaa1d +bff53c1884416970604fefe79c906b57fba9dec826b37fd83ff609e530ff5fe8
diff --git a/a/1.txt b/N3/1.txt index dd89691..6a754e6 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,7 +1,7 @@ On Thu, Dec 14, 2023, Maxim Levitsky wrote: > On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote: > > On Sun, Dec 10, 2023, Jim Mattson wrote: -> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote: +> > > On Thu, Dec 7, 2023 at 8:21 AM Sean Christopherson <seanjc@google.com> wrote: > > > > Doh. We got the less obvious cases and missed the obvious one. > > > > > > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That diff --git a/a/content_digest b/N3/content_digest index 16a5c3a..fd7ede3 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -5,15 +5,39 @@ "ref\0ZXh8Nq_y_szj1WN0@google.com\0" "ref\05ca5592b21131f515e296afae006e5bb28b1fb87.camel@redhat.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" + "Subject\0Re: [PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" "Date\0Wed, 13 Dec 2023 14:59:16 -0800\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Maxim Levitsky <mlevitsk@redhat.com>\0" + "Cc\0kvm@vger.kernel.org" + david@redhat.com + atishp@atishpatra.org + linux-mips@vger.kernel.org + linux-riscv@lists.infradead.org + imbrenda@linux.ibm.com + frankja@linux.ibm.com + maz@kernel.org + chenhuacai@kernel.org + palmer@dabbelt.com + borntraeger@linux.ibm.com + aou@eecs.berkeley.edu + suzuki.poulose@arm.com + paul.walmsley@sifive.com + alexandru.elisei@arm.com + linux-arm-kernel@lists.infradead.org + Jim Mattson <jmattson@google.com> + linux-kernel@vger.kernel.org + oliver.upton@linux.dev + james.morse@arm.com + kvm-riscv@lists.infradead.org + anup@brainfault.org + pbonzini@redhat.com + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On Thu, Dec 14, 2023, Maxim Levitsky wrote:\n" "> On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote:\n" "> > On Sun, Dec 10, 2023, Jim Mattson wrote:\n" - "> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote:\n" + "> > > On Thu, Dec 7, 2023 at 8:21\342\200\257AM Sean Christopherson <seanjc@google.com> wrote:\n" "> > > > Doh. We got the less obvious cases and missed the obvious one.\n" "> > > > \n" "> > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That\n" @@ -84,4 +108,4 @@ "nested virtualization awareness because the event itself is tracked for the vCPU\n" as a whole. -364b412e251e40594b2edb84d415468a2ae371edc91ba665cdbae8df24ecaa1d +b07d0e30e83d0d0d84390f63d4aa0d6032b57b98c1227fc77c574405858f78e8
diff --git a/a/1.txt b/N4/1.txt index dd89691..41fa65d 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -1,7 +1,7 @@ On Thu, Dec 14, 2023, Maxim Levitsky wrote: > On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote: > > On Sun, Dec 10, 2023, Jim Mattson wrote: -> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote: +> > > On Thu, Dec 7, 2023 at 8:21 AM Sean Christopherson <seanjc@google.com> wrote: > > > > Doh. We got the less obvious cases and missed the obvious one. > > > > > > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That @@ -71,3 +71,8 @@ to L2, e.g. nVMX's preemption timer, MTF, and pending virtual interrupts (hmm, I suspect nSVM's vNMI is broken too). Things like INIT and SMI don't require nested virtualization awareness because the event itself is tracked for the vCPU as a whole. + +_______________________________________________ +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/N4/content_digest index 16a5c3a..ecb7279 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -5,15 +5,39 @@ "ref\0ZXh8Nq_y_szj1WN0@google.com\0" "ref\05ca5592b21131f515e296afae006e5bb28b1fb87.camel@redhat.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" + "Subject\0Re: [PATCH v4 10/12] KVM: x86: never write to memory from kvm_vcpu_check_block()\0" "Date\0Wed, 13 Dec 2023 14:59:16 -0800\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Maxim Levitsky <mlevitsk@redhat.com>\0" + "Cc\0Jim Mattson <jmattson@google.com>" + alexandru.elisei@arm.com + anup@brainfault.org + aou@eecs.berkeley.edu + atishp@atishpatra.org + borntraeger@linux.ibm.com + chenhuacai@kernel.org + david@redhat.com + frankja@linux.ibm.com + imbrenda@linux.ibm.com + james.morse@arm.com + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + linux-kernel@vger.kernel.org + linux-mips@vger.kernel.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + maz@kernel.org + oliver.upton@linux.dev + palmer@dabbelt.com + paul.walmsley@sifive.com + pbonzini@redhat.com + " suzuki.poulose@arm.com\0" "\00:1\0" "b\0" "On Thu, Dec 14, 2023, Maxim Levitsky wrote:\n" "> On Tue, 2023-12-12 at 07:28 -0800, Sean Christopherson wrote:\n" "> > On Sun, Dec 10, 2023, Jim Mattson wrote:\n" - "> > > On Thu, Dec 7, 2023 at 8:21?AM Sean Christopherson <seanjc@google.com> wrote:\n" + "> > > On Thu, Dec 7, 2023 at 8:21\342\200\257AM Sean Christopherson <seanjc@google.com> wrote:\n" "> > > > Doh. We got the less obvious cases and missed the obvious one.\n" "> > > > \n" "> > > > Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt(). That\n" @@ -82,6 +106,11 @@ "to L2, e.g. nVMX's preemption timer, MTF, and pending virtual interrupts (hmm,\n" "I suspect nSVM's vNMI is broken too). Things like INIT and SMI don't require\n" "nested virtualization awareness because the event itself is tracked for the vCPU\n" - as a whole. + "as a whole.\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 -364b412e251e40594b2edb84d415468a2ae371edc91ba665cdbae8df24ecaa1d +0a86db822c0786c5c76ba8f87430c97eb0bb34e70a9e5f35319a3ce5c9bb0275
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.