All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <YXllGfrjPX1pVUx6@google.com>

diff --git a/a/1.txt b/N1/1.txt
index e714195..80cd8cb 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,7 +3,7 @@ On Mon, Oct 25, 2021, Paolo Bonzini wrote:
 > Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,
 > but I have to think more about whether I agree with it.
 
-https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com
+https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com
 
 > In reality the CMPXCHG loops can really fail just once, because they only
 > race with the processor setting ON=1.  But if the warnings were to trigger
diff --git a/a/content_digest b/N1/content_digest
index 3560477..e14a5e3 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,9 +1,41 @@
  "ref\020211009021236.4122790-1-seanjc@google.com\0"
  "ref\0614858dd-106c-64cc-04bc-f1887b2054d1@redhat.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
+ "Subject\0Re: [PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
  "Date\0Wed, 27 Oct 2021 14:41:29 +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 Mon, Oct 25, 2021, Paolo Bonzini wrote:\n"
@@ -11,7 +43,7 @@
  "> Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,\n"
  "> but I have to think more about whether I agree with it.\n"
  "\n"
- "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com\n"
+ "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com\n"
  "\n"
  "> In reality the CMPXCHG loops can really fail just once, because they only\n"
  "> race with the processor setting ON=1.  But if the warnings were to trigger\n"
@@ -34,4 +66,4 @@
  "double list add with VT-d posted interrupts\").  Then it would be at least plausible\n"
  that a vCPU could mess up its own descriptor while being scheduled out/in.
 
-0af9b1e4454a65b6ce4e7c63d363c27ac4746aca5d02ffed98c295422e1745df
+e0a561149b361e78ceb3904df58380a011b1eeadf9d8808ecfafb0cf8ccaa86c

diff --git a/a/1.txt b/N2/1.txt
index e714195..f72d2bf 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -3,7 +3,7 @@ On Mon, Oct 25, 2021, Paolo Bonzini wrote:
 > Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,
 > but I have to think more about whether I agree with it.
 
-https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com
+https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com
 
 > In reality the CMPXCHG loops can really fail just once, because they only
 > race with the processor setting ON=1.  But if the warnings were to trigger
@@ -25,3 +25,7 @@ wrong and confusing (for me).  The WARNs in the loops made more sense when the
 loops ran with IRQs enabled prior to commit 8b306e2f3c41 ("KVM: VMX: avoid
 double list add with VT-d posted interrupts").  Then it would be at least plausible
 that a vCPU could mess up its own descriptor while being scheduled out/in.
+_______________________________________________
+kvmarm mailing list
+kvmarm@lists.cs.columbia.edu
+https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
diff --git a/a/content_digest b/N2/content_digest
index 3560477..b05b7af 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,36 @@
  "ref\020211009021236.4122790-1-seanjc@google.com\0"
  "ref\0614858dd-106c-64cc-04bc-f1887b2054d1@redhat.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
+ "Subject\0Re: [PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
  "Date\0Wed, 27 Oct 2021 14:41:29 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Paolo Bonzini <pbonzini@redhat.com>\0"
+ "Cc\0Cornelia Huck <cohuck@redhat.com>"
+  Wanpeng Li <wanpengli@tencent.com>
+  kvm@vger.kernel.org
+  David Hildenbrand <david@redhat.com>
+  linux-kernel@vger.kernel.org
+  Paul Mackerras <paulus@ozlabs.org>
+  Atish Patra <atish.patra@wdc.com>
+  linux-riscv@lists.infradead.org
+  Claudio Imbrenda <imbrenda@linux.ibm.com>
+  kvmarm@lists.cs.columbia.edu
+  Janosch Frank <frankja@linux.ibm.com>
+  Marc Zyngier <maz@kernel.org>
+  Joerg Roedel <joro@8bytes.org>
+  Huacai Chen <chenhuacai@kernel.org>
+  Christian Borntraeger <borntraeger@de.ibm.com>
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  kvm-ppc@vger.kernel.org
+  Paul Walmsley <paul.walmsley@sifive.com>
+  David Matlack <dmatlack@google.com>
+  linux-arm-kernel@lists.infradead.org
+  Jim Mattson <jmattson@google.com>
+  Anup Patel <anup.patel@wdc.com>
+  linux-mips@vger.kernel.org
+  Palmer Dabbelt <palmer@dabbelt.com>
+  kvm-riscv@lists.infradead.org
+ " Vitaly Kuznetsov <vkuznets@redhat.com>\0"
  "\00:1\0"
  "b\0"
  "On Mon, Oct 25, 2021, Paolo Bonzini wrote:\n"
@@ -11,7 +38,7 @@
  "> Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,\n"
  "> but I have to think more about whether I agree with it.\n"
  "\n"
- "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com\n"
+ "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com\n"
  "\n"
  "> In reality the CMPXCHG loops can really fail just once, because they only\n"
  "> race with the processor setting ON=1.  But if the warnings were to trigger\n"
@@ -32,6 +59,10 @@
  "wrong and confusing (for me).  The WARNs in the loops made more sense when the\n"
  "loops ran with IRQs enabled prior to commit 8b306e2f3c41 (\"KVM: VMX: avoid\n"
  "double list add with VT-d posted interrupts\").  Then it would be at least plausible\n"
- that a vCPU could mess up its own descriptor while being scheduled out/in.
+ "that a vCPU could mess up its own descriptor while being scheduled out/in.\n"
+ "_______________________________________________\n"
+ "kvmarm mailing list\n"
+ "kvmarm@lists.cs.columbia.edu\n"
+ https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
 
-0af9b1e4454a65b6ce4e7c63d363c27ac4746aca5d02ffed98c295422e1745df
+2f664567c90b89c44272b727d40fe37cf52ea7efb451f0c403f0530ab2fac0e1

diff --git a/a/1.txt b/N3/1.txt
index e714195..710e9f7 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -3,7 +3,7 @@ On Mon, Oct 25, 2021, Paolo Bonzini wrote:
 > Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,
 > but I have to think more about whether I agree with it.
 
-https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com
+https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com
 
 > In reality the CMPXCHG loops can really fail just once, because they only
 > race with the processor setting ON=1.  But if the warnings were to trigger
@@ -25,3 +25,8 @@ wrong and confusing (for me).  The WARNs in the loops made more sense when the
 loops ran with IRQs enabled prior to commit 8b306e2f3c41 ("KVM: VMX: avoid
 double list add with VT-d posted interrupts").  Then it would be at least plausible
 that a vCPU could mess up its own descriptor while being scheduled out/in.
+
+_______________________________________________
+linux-riscv mailing list
+linux-riscv@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/a/content_digest b/N3/content_digest
index 3560477..6dd1ed3 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -1,9 +1,41 @@
  "ref\020211009021236.4122790-1-seanjc@google.com\0"
  "ref\0614858dd-106c-64cc-04bc-f1887b2054d1@redhat.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
+ "Subject\0Re: [PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
  "Date\0Wed, 27 Oct 2021 14:41:29 +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 Mon, Oct 25, 2021, Paolo Bonzini wrote:\n"
@@ -11,7 +43,7 @@
  "> Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,\n"
  "> but I have to think more about whether I agree with it.\n"
  "\n"
- "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com\n"
+ "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com\n"
  "\n"
  "> In reality the CMPXCHG loops can really fail just once, because they only\n"
  "> race with the processor setting ON=1.  But if the warnings were to trigger\n"
@@ -32,6 +64,11 @@
  "wrong and confusing (for me).  The WARNs in the loops made more sense when the\n"
  "loops ran with IRQs enabled prior to commit 8b306e2f3c41 (\"KVM: VMX: avoid\n"
  "double list add with VT-d posted interrupts\").  Then it would be at least plausible\n"
- that a vCPU could mess up its own descriptor while being scheduled out/in.
+ "that a vCPU could mess up its own descriptor while being scheduled out/in.\n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-0af9b1e4454a65b6ce4e7c63d363c27ac4746aca5d02ffed98c295422e1745df
+5dcc89c165c5a95183b92e1fe90f53691dc4e83df463e58bcc65a5bee17fc9c6

diff --git a/a/1.txt b/N4/1.txt
index e714195..6f17b1a 100644
--- a/a/1.txt
+++ b/N4/1.txt
@@ -3,7 +3,7 @@ On Mon, Oct 25, 2021, Paolo Bonzini wrote:
 > Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,
 > but I have to think more about whether I agree with it.
 
-https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com
+https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com
 
 > In reality the CMPXCHG loops can really fail just once, because they only
 > race with the processor setting ON=1.  But if the warnings were to trigger
@@ -25,3 +25,8 @@ wrong and confusing (for me).  The WARNs in the loops made more sense when the
 loops ran with IRQs enabled prior to commit 8b306e2f3c41 ("KVM: VMX: avoid
 double list add with VT-d posted interrupts").  Then it would be at least plausible
 that a vCPU could mess up its own descriptor while being scheduled out/in.
+
+_______________________________________________
+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 3560477..5a36074 100644
--- a/a/content_digest
+++ b/N4/content_digest
@@ -1,9 +1,41 @@
  "ref\020211009021236.4122790-1-seanjc@google.com\0"
  "ref\0614858dd-106c-64cc-04bc-f1887b2054d1@redhat.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
+ "Subject\0Re: [PATCH v2 00/43] KVM: Halt-polling and x86 APICv overhaul\0"
  "Date\0Wed, 27 Oct 2021 14:41:29 +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 Mon, Oct 25, 2021, Paolo Bonzini wrote:\n"
@@ -11,7 +43,7 @@
  "> Queued 1-20 and 22-28.  Initially I skipped 21 because I didn't receive it,\n"
  "> but I have to think more about whether I agree with it.\n"
  "\n"
- "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc at google.com\n"
+ "https://lkml.kernel.org/r/20211009021236.4122790-22-seanjc@google.com\n"
  "\n"
  "> In reality the CMPXCHG loops can really fail just once, because they only\n"
  "> race with the processor setting ON=1.  But if the warnings were to trigger\n"
@@ -32,6 +64,11 @@
  "wrong and confusing (for me).  The WARNs in the loops made more sense when the\n"
  "loops ran with IRQs enabled prior to commit 8b306e2f3c41 (\"KVM: VMX: avoid\n"
  "double list add with VT-d posted interrupts\").  Then it would be at least plausible\n"
- that a vCPU could mess up its own descriptor while being scheduled out/in.
+ "that a vCPU could mess up its own descriptor while being scheduled out/in.\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
 
-0af9b1e4454a65b6ce4e7c63d363c27ac4746aca5d02ffed98c295422e1745df
+7ce1da47b01b00735bea57d3cced172c79e7390999074c08dacf334f9512fd31

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.