diff for duplicates of <YXl5anv0Lyjx1cws@google.com>

diff --git a/a/1.txt b/N1/1.txt
index 534dca0..822f624 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,7 +1,7 @@
 On Wed, Oct 27, 2021, Paolo Bonzini wrote:
 > On 27/10/21 17:06, Sean Christopherson wrote:
 > > > Does this still need to check the "running" flag?  That should be a strict
-> > > superset of vcpu->mode == IN_GUEST_MODE.
+> > > superset of vcpu->mode = IN_GUEST_MODE.
 > > 
 > > No.  Signalling the doorbell when "running" is set but the vCPU is not in the
 > > guest is just an expensive nop.  So even if KVM were to rework its handling of
@@ -25,5 +25,5 @@ I completely misunderstanding what your referring to?
 +        * is in the guest.  If the vCPU is not in the guest, hardware will
 +        * automatically process AVIC interrupts at VMRUN.
 +        */
-+       if (vcpu->mode == IN_GUEST_MODE) {
++       if (vcpu->mode = IN_GUEST_MODE) {
                 int cpu = READ_ONCE(vcpu->cpu);
diff --git a/a/content_digest b/N1/content_digest
index 883fe77..c0e66f5 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,15 +4,47 @@
  "ref\0YXlrEWmBohaDXmqL@google.com\0"
  "ref\0185502d7-861e-fa5c-b225-419710fe77ed@redhat.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v2 35/43] KVM: SVM: Signal AVIC doorbell iff vCPU is in guest mode\0"
+ "Subject\0Re: [PATCH v2 35/43] KVM: SVM: Signal AVIC doorbell iff vCPU is in guest mode\0"
  "Date\0Wed, 27 Oct 2021 16:08:10 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\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>
+  Anup Patel <anup.patel@wdc.com>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  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>
+  Atish Patra <atish.patra@wdc.com>
+  David Hildenbrand <david@redhat.com>
+  Cornelia Huck <cohuck@redhat.com>
+  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
+  kvm-ppc@vger.kernel.org
+  kvm-riscv@lists.infradead.org
+  linux-riscv@lists.infradead.org
+  linux-kernel@vger.kernel.org
+  David Matlack <dmatlack@google.com>
+  Oliver Upton <oupton@google.com>
+ " Jing Zhang <jingzhangos@google.com>\0"
  "\00:1\0"
  "b\0"
  "On Wed, Oct 27, 2021, Paolo Bonzini wrote:\n"
  "> On 27/10/21 17:06, Sean Christopherson wrote:\n"
  "> > > Does this still need to check the \"running\" flag?  That should be a strict\n"
- "> > > superset of vcpu->mode == IN_GUEST_MODE.\n"
+ "> > > superset of vcpu->mode = IN_GUEST_MODE.\n"
  "> > \n"
  "> > No.  Signalling the doorbell when \"running\" is set but the vCPU is not in the\n"
  "> > guest is just an expensive nop.  So even if KVM were to rework its handling of\n"
@@ -36,7 +68,7 @@
  "+        * is in the guest.  If the vCPU is not in the guest, hardware will\n"
  "+        * automatically process AVIC interrupts at VMRUN.\n"
  "+        */\n"
- "+       if (vcpu->mode == IN_GUEST_MODE) {\n"
+ "+       if (vcpu->mode = IN_GUEST_MODE) {\n"
                  int cpu = READ_ONCE(vcpu->cpu);
 
-183f77a2dce0b6df4ba2c3d75663a9e30c27bb101e1d0c3a160987445d593a5a
+b4b2beff54d382db3f151fc24d794764cbadfa1c3a6a600167159e3f45229e06
