diff for duplicates of <Y3PzhANShVlTXVg1@google.com>

diff --git a/a/1.txt b/N1/1.txt
index 314b62a..6bfcaf3 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,9 +2,9 @@ On Thu, Nov 10, 2022, Huang, Kai wrote:
 > On Thu, 2022-11-10 at 01:33 +0000, Huang, Kai wrote:
 > > > @@ -9283,7 +9283,13 @@ static int
 > > > kvm_x86_check_processor_compatibility(struct kvm_x86_init_ops *ops)
-> > > ?	int cpu = smp_processor_id();
-> > > ?	struct cpuinfo_x86 *c = &cpu_data(cpu);
-> > > ?
+> > >  	int cpu = smp_processor_id();
+> > >  	struct cpuinfo_x86 *c = &cpu_data(cpu);
+> > >  
 > > > -	WARN_ON(!irqs_disabled());
 > > > +	/*
 > > > +	 * Compatibility checks are done when loading KVM and when enabling
@@ -14,7 +14,7 @@ On Thu, Nov 10, 2022, Huang, Kai wrote:
 > > > +	 * an offline CPU.
 > > > +	 */
 > > > +	WARN_ON(!irqs_disabled() && cpu_active(cpu));
-> > > ?
+> > >  
 > > 
 > > Also, the logic of:
 > > 
@@ -27,7 +27,7 @@ On Thu, Nov 10, 2022, Huang, Kai wrote:
 > > the IRQ is indeed disabled.
 > > 
 > > But this doesn't make sense anymore after we move to ONLINE section, in which
-> > IRQ has already been enabled (see start_secondary()).? IIUC the WARN_ON()
+> > IRQ has already been enabled (see start_secondary()).  IIUC the WARN_ON()
 > > doesn't get exploded is purely because there's an additional cpu_active(cpu)
 > > check.
 > > 
@@ -54,3 +54,7 @@ the reason for that is because you're wrong about the hotplug case.  In this ver
 of things, the compatibility checks are routed through hardware enabling, i.e. this
 flow is used only when loading KVM.  This helper should only be called via SMP function
 call, which means that IRQs should always be disabled.
+_______________________________________________
+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 6c5c63a..61a069e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,18 +3,53 @@
  "ref\088e920944de70e7d69a98f74005b49c59b5aaa3b.camel@intel.com\0"
  "ref\0b198fe971cecd301f0c7c66028cfd71dd7ba7e62.camel@intel.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 38/44] KVM: Disable CPU hotplug during hardware enabling\0"
+ "Subject\0Re: [PATCH 38/44] KVM: Disable CPU hotplug during hardware enabling\0"
  "Date\0Tue, 15 Nov 2022 20:16:04 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Huang"
+ " Kai <kai.huang@intel.com>\0"
+ "Cc\0mjrosato@linux.ibm.com <mjrosato@linux.ibm.com>"
+  david@redhat.com <david@redhat.com>
+  Yao
+  Yuan <yuan.yao@intel.com>
+  paul.walmsley@sifive.com <paul.walmsley@sifive.com>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  mpe@ellerman.id.au <mpe@ellerman.id.au>
+  linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>
+  imbrenda@linux.ibm.com <imbrenda@linux.ibm.com>
+  kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu>
+  linux-s390@vger.kernel.org <linux-s390@vger.kernel.org>
+  frankja@linux.ibm.com <frankja@linux.ibm.com>
+  maz@kernel.org <maz@kernel.org>
+  chenhuacai@kernel.org <chenhuacai@kernel.org>
+  aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com>
+  borntraeger@linux.ibm.com <borntraeger@linux.ibm.com>
+  Gao
+  Chao <chao.gao@intel.com>
+  farman@linux.ibm.com <farman@linux.ibm.com>
+  aou@eecs.berkeley.edu <aou@eecs.berkeley.edu>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  atishp@atishpatra.org <atishp@atishpatra.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  tglx@linutronix.de <tglx@linutronix.de>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  Yamahata
+  Isaku <isaku.yamahata@intel.com>
+  farosas@linux.ibm.com <farosas@linux.ibm.com>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  palmer@dabbelt.com <palmer@dabbelt.com>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+  pbonzini@redhat.com <pbonzini@redhat.com>
+  vkuznets@redhat.com <vkuznets@redhat.com>
+ " linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org>\0"
  "\00:1\0"
  "b\0"
  "On Thu, Nov 10, 2022, Huang, Kai wrote:\n"
  "> On Thu, 2022-11-10 at 01:33 +0000, Huang, Kai wrote:\n"
  "> > > @@ -9283,7 +9283,13 @@ static int\n"
  "> > > kvm_x86_check_processor_compatibility(struct kvm_x86_init_ops *ops)\n"
- "> > > ?\tint cpu = smp_processor_id();\n"
- "> > > ?\tstruct cpuinfo_x86 *c = &cpu_data(cpu);\n"
- "> > > ?\n"
+ "> > > \302\240\tint cpu = smp_processor_id();\n"
+ "> > > \302\240\tstruct cpuinfo_x86 *c = &cpu_data(cpu);\n"
+ "> > > \302\240\n"
  "> > > -\tWARN_ON(!irqs_disabled());\n"
  "> > > +\t/*\n"
  "> > > +\t * Compatibility checks are done when loading KVM and when enabling\n"
@@ -24,7 +59,7 @@
  "> > > +\t * an offline CPU.\n"
  "> > > +\t */\n"
  "> > > +\tWARN_ON(!irqs_disabled() && cpu_active(cpu));\n"
- "> > > ?\n"
+ "> > > \302\240\n"
  "> > \n"
  "> > Also, the logic of:\n"
  "> > \n"
@@ -37,7 +72,7 @@
  "> > the IRQ is indeed disabled.\n"
  "> > \n"
  "> > But this doesn't make sense anymore after we move to ONLINE section, in which\n"
- "> > IRQ has already been enabled (see start_secondary()).? IIUC the WARN_ON()\n"
+ "> > IRQ has already been enabled (see start_secondary()).\302\240 IIUC the WARN_ON()\n"
  "> > doesn't get exploded is purely because there's an additional cpu_active(cpu)\n"
  "> > check.\n"
  "> > \n"
@@ -63,6 +98,10 @@
  "the reason for that is because you're wrong about the hotplug case.  In this version\n"
  "of things, the compatibility checks are routed through hardware enabling, i.e. this\n"
  "flow is used only when loading KVM.  This helper should only be called via SMP function\n"
- call, which means that IRQs should always be disabled.
+ "call, which means that IRQs should always be disabled.\n"
+ "_______________________________________________\n"
+ "kvmarm mailing list\n"
+ "kvmarm@lists.cs.columbia.edu\n"
+ https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
 
-e0cb11509840f6884d91018f831cf79f61dcbb98c09ee339b718532b800cc5ac
+9606b843a2ce3c2054f4be984dc6d6cac916e2eae608b86da2162e952b76b9eb
