diff for duplicates of <YVNA+KTbLrxGQ6ML@google.com> diff --git a/a/1.txt b/N1/1.txt index d04c003..d83edf7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -91,7 +91,7 @@ Ignoring the kvm_arch_dy_runnable() case for the moment, how would it lead to corruption? The idea is that the 'vmcr_available' flag would be cleared when the vCPU is run, i.e. it tracks whether or not the shadow state may be stale. -> > if (kvm_vgic_global_state.type = VGIC_V2) +> > if (kvm_vgic_global_state.type == VGIC_V2) > > vgic_v2_get_vmcr(vcpu, vmcr); > > else > > @@ -223,3 +223,12 @@ index 275a27368a04..9870e824a27e 100644 } kvm_incr_pc(vcpu); + + + + + +_______________________________________________ +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 18d28c6..58a131b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,30 +9,26 @@ "Subject\0Re: [PATCH 07/14] KVM: Don't block+unblock when halt-polling is successful\0" "Date\0Tue, 28 Sep 2021 16:21:12 +0000\0" "To\0Marc Zyngier <maz@kernel.org>\0" - "Cc\0Paolo Bonzini <pbonzini@redhat.com>" - Huacai Chen <chenhuacai@kernel.org> - Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> - Paul Mackerras <paulus@ozlabs.org> - Christian Borntraeger <borntraeger@de.ibm.com> - Janosch Frank <frankja@linux.ibm.com> - James Morse <james.morse@arm.com> - Alexandru Elisei <alexandru.elisei@arm.com> - Suzuki K Poulose <suzuki.poulose@arm.com> + "Cc\0Wanpeng Li <wanpengli@tencent.com>" + kvm@vger.kernel.org David Hildenbrand <david@redhat.com> - Cornelia Huck <cohuck@redhat.com> + linux-kernel@vger.kernel.org + Paul Mackerras <paulus@ozlabs.org> Claudio Imbrenda <imbrenda@linux.ibm.com> - Vitaly Kuznetsov <vkuznets@redhat.com> - Wanpeng Li <wanpengli@tencent.com> - Jim Mattson <jmattson@google.com> - Joerg Roedel <joro@8bytes.org> - linux-arm-kernel@lists.infradead.org kvmarm@lists.cs.columbia.edu - linux-mips@vger.kernel.org - kvm@vger.kernel.org + Janosch Frank <frankja@linux.ibm.com> + Joerg Roedel <joro@8bytes.org> + Huacai Chen <chenhuacai@kernel.org> + Christian Borntraeger <borntraeger@de.ibm.com> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> kvm-ppc@vger.kernel.org - linux-kernel@vger.kernel.org David Matlack <dmatlack@google.com> - " Jing Zhang <jingzhangos@google.com>\0" + linux-arm-kernel@lists.infradead.org + Jim Mattson <jmattson@google.com> + Cornelia Huck <cohuck@redhat.com> + linux-mips@vger.kernel.org + Paolo Bonzini <pbonzini@redhat.com> + " Vitaly Kuznetsov <vkuznets@redhat.com>\0" "\00:1\0" "b\0" "On Tue, Sep 28, 2021, Marc Zyngier wrote:\n" @@ -128,7 +124,7 @@ "corruption? The idea is that the 'vmcr_available' flag would be cleared when the\n" "vCPU is run, i.e. it tracks whether or not the shadow state may be stale.\n" "\n" - "> > if (kvm_vgic_global_state.type = VGIC_V2)\n" + "> > if (kvm_vgic_global_state.type == VGIC_V2)\n" "> > vgic_v2_get_vmcr(vcpu, vmcr);\n" "> > else\n" "> > \n" @@ -259,6 +255,15 @@ "+ preempt_enable();\n" " }\n" "\n" - kvm_incr_pc(vcpu); + " kvm_incr_pc(vcpu);\n" + "\n" + "\n" + "\n" + "\n" + "\n" + "_______________________________________________\n" + "kvmarm mailing list\n" + "kvmarm@lists.cs.columbia.edu\n" + https://lists.cs.columbia.edu/mailman/listinfo/kvmarm -42009671ebe996bc821bb4a8a8904f853e7f1befc879fd131f0ac19b5f1a16e2 +15a5ef2be8bda706f8afce2b6bbdc5e5258ab2127ca20097a66d638c0f80330d
diff --git a/a/1.txt b/N2/1.txt index d04c003..e84865d 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -91,7 +91,7 @@ Ignoring the kvm_arch_dy_runnable() case for the moment, how would it lead to corruption? The idea is that the 'vmcr_available' flag would be cleared when the vCPU is run, i.e. it tracks whether or not the shadow state may be stale. -> > if (kvm_vgic_global_state.type = VGIC_V2) +> > if (kvm_vgic_global_state.type == VGIC_V2) > > vgic_v2_get_vmcr(vcpu, vmcr); > > else > > diff --git a/a/content_digest b/N2/content_digest index 18d28c6..754b14c 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -128,7 +128,7 @@ "corruption? The idea is that the 'vmcr_available' flag would be cleared when the\n" "vCPU is run, i.e. it tracks whether or not the shadow state may be stale.\n" "\n" - "> > if (kvm_vgic_global_state.type = VGIC_V2)\n" + "> > if (kvm_vgic_global_state.type == VGIC_V2)\n" "> > vgic_v2_get_vmcr(vcpu, vmcr);\n" "> > else\n" "> > \n" @@ -261,4 +261,4 @@ "\n" kvm_incr_pc(vcpu); -42009671ebe996bc821bb4a8a8904f853e7f1befc879fd131f0ac19b5f1a16e2 +d9fa820fb72ff8a12eaa43c2a6205d19eb582b9b071a9518ea299643ebfb37d2
diff --git a/a/1.txt b/N3/1.txt index d04c003..991ad1d 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -91,7 +91,7 @@ Ignoring the kvm_arch_dy_runnable() case for the moment, how would it lead to corruption? The idea is that the 'vmcr_available' flag would be cleared when the vCPU is run, i.e. it tracks whether or not the shadow state may be stale. -> > if (kvm_vgic_global_state.type = VGIC_V2) +> > if (kvm_vgic_global_state.type == VGIC_V2) > > vgic_v2_get_vmcr(vcpu, vmcr); > > else > > @@ -223,3 +223,13 @@ index 275a27368a04..9870e824a27e 100644 } kvm_incr_pc(vcpu); + + + + + + +_______________________________________________ +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 18d28c6..fa16b53 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -128,7 +128,7 @@ "corruption? The idea is that the 'vmcr_available' flag would be cleared when the\n" "vCPU is run, i.e. it tracks whether or not the shadow state may be stale.\n" "\n" - "> > if (kvm_vgic_global_state.type = VGIC_V2)\n" + "> > if (kvm_vgic_global_state.type == VGIC_V2)\n" "> > vgic_v2_get_vmcr(vcpu, vmcr);\n" "> > else\n" "> > \n" @@ -259,6 +259,16 @@ "+ preempt_enable();\n" " }\n" "\n" - kvm_incr_pc(vcpu); + " kvm_incr_pc(vcpu);\n" + "\n" + "\n" + "\n" + "\n" + "\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 -42009671ebe996bc821bb4a8a8904f853e7f1befc879fd131f0ac19b5f1a16e2 +ba09084bd61caf3fb16b0854466f0c1d42d23ec9304079171176070bf1a4e184
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.