diff for duplicates of <87sfikmuop.fsf@redhat.com> diff --git a/a/1.txt b/N1/1.txt index 079f3f3..219e74b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -76,7 +76,7 @@ Sean Christopherson <seanjc@google.com> writes: It seems we can't get away without a dedicated stage for Hyper-V anyway, e.g. see our discussion with Michael: -https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/ +https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/ All these issues are more or less "theoretical" as there's no real CPU hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by @@ -211,3 +211,8 @@ Thanks for looking into this! -- Vitaly + +_______________________________________________ +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 9912604..ea5e2a4 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,9 +3,39 @@ "ref\087mt98qfi2.fsf@ovpn-194-252.brq.redhat.com\0" "ref\0Y22nrQ7aziK0NMOE@google.com\0" "From\0Vitaly Kuznetsov <vkuznets@redhat.com>\0" - "Subject\0[PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" + "Subject\0Re: [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" "Date\0Tue, 15 Nov 2022 10:30:14 +0100\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0kvm@vger.kernel.org" + David Hildenbrand <david@redhat.com> + Atish Patra <atishp@atishpatra.org> + linux-kernel@vger.kernel.org + linux-riscv@lists.infradead.org + Claudio Imbrenda <imbrenda@linux.ibm.com> + kvmarm@lists.cs.columbia.edu + linux-s390@vger.kernel.org + Janosch Frank <frankja@linux.ibm.com> + Michael Ellerman <mpe@ellerman.id.au> + Huacai Chen <chenhuacai@kernel.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + Palmer Dabbelt <palmer@dabbelt.com> + Christian Borntraeger <borntraeger@linux.ibm.com> + Matthew Rosato <mjrosato@linux.ibm.com> + Chao Gao <chao.gao@intel.com> + Eric Farman <farman@linux.ibm.com> + Albert Ou <aou@eecs.berkeley.edu> + Paul Walmsley <paul.walmsley@sifive.com> + Yuan Yao <yuan.yao@intel.com> + kvmarm@lists.linux.dev + Thomas Gleixner <tglx@linutronix.de> + linux-arm-kernel@lists.infradead.org + Isaku Yamahata <isaku.yamahata@intel.com> + Fabiano Rosas <farosas@linux.ibm.com> + linux-mips@vger.kernel.org + kvm-riscv@lists.infradead.org + Marc Zyngier <maz@kernel.org> + Paolo Bonzini <pbonzini@redhat.com> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "Sean Christopherson <seanjc@google.com> writes:\n" @@ -86,7 +116,7 @@ "It seems we can't get away without a dedicated stage for Hyper-V anyway,\n" "e.g. see our discussion with Michael:\n" "\n" - "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/\n" + "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/\n" "\n" "All these issues are more or less \"theoretical\" as there's no real CPU\n" "hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by\n" @@ -220,6 +250,11 @@ "> base-commit: 5f47ba6894477dfbdc5416467a25fb7acb47d404\n" "\n" "-- \n" - Vitaly + "Vitaly\n" + "\n" + "_______________________________________________\n" + "kvmarm mailing list\n" + "kvmarm@lists.cs.columbia.edu\n" + https://lists.cs.columbia.edu/mailman/listinfo/kvmarm -91596a555581c66f9035665e010006c9886d44491fcc7adb3cc34d005d3aa7ad +e90e2c5c00ff4e0b0ff02f89c28ed0708cff67c57063f1e2ce6ec1159eabb65b
diff --git a/a/1.txt b/N2/1.txt index 079f3f3..7a53541 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -76,7 +76,7 @@ Sean Christopherson <seanjc@google.com> writes: It seems we can't get away without a dedicated stage for Hyper-V anyway, e.g. see our discussion with Michael: -https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/ +https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/ All these issues are more or less "theoretical" as there's no real CPU hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by diff --git a/a/content_digest b/N2/content_digest index 9912604..14a509d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,9 +3,44 @@ "ref\087mt98qfi2.fsf@ovpn-194-252.brq.redhat.com\0" "ref\0Y22nrQ7aziK0NMOE@google.com\0" "From\0Vitaly Kuznetsov <vkuznets@redhat.com>\0" - "Subject\0[PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" + "Subject\0Re: [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" "Date\0Tue, 15 Nov 2022 10:30:14 +0100\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0James Morse <james.morse@arm.com>" + Alexandru Elisei <alexandru.elisei@arm.com> + Suzuki K Poulose <suzuki.poulose@arm.com> + Oliver Upton <oliver.upton@linux.dev> + Atish Patra <atishp@atishpatra.org> + David Hildenbrand <david@redhat.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + kvmarm@lists.cs.columbia.edu + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-s390@vger.kernel.org + linux-kernel@vger.kernel.org + Isaku Yamahata <isaku.yamahata@intel.com> + Fabiano Rosas <farosas@linux.ibm.com> + Michael Ellerman <mpe@ellerman.id.au> + Chao Gao <chao.gao@intel.com> + Thomas Gleixner <tglx@linutronix.de> + Yuan Yao <yuan.yao@intel.com> + Paolo Bonzini <pbonzini@redhat.com> + Marc Zyngier <maz@kernel.org> + Huacai Chen <chenhuacai@kernel.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Christian Borntraeger <borntraeger@linux.ibm.com> + Janosch Frank <frankja@linux.ibm.com> + Claudio Imbrenda <imbrenda@linux.ibm.com> + Matthew Rosato <mjrosato@linux.ibm.com> + " Eric Farman <farman@linux.ibm.com>\0" "\00:1\0" "b\0" "Sean Christopherson <seanjc@google.com> writes:\n" @@ -86,7 +121,7 @@ "It seems we can't get away without a dedicated stage for Hyper-V anyway,\n" "e.g. see our discussion with Michael:\n" "\n" - "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/\n" + "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/\n" "\n" "All these issues are more or less \"theoretical\" as there's no real CPU\n" "hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by\n" @@ -222,4 +257,4 @@ "-- \n" Vitaly -91596a555581c66f9035665e010006c9886d44491fcc7adb3cc34d005d3aa7ad +acae7cecc6bb177cb01d87e610995de108ac97e71beb73be7eb476df31965877
diff --git a/a/1.txt b/N3/1.txt index 079f3f3..04585ac 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -76,7 +76,7 @@ Sean Christopherson <seanjc@google.com> writes: It seems we can't get away without a dedicated stage for Hyper-V anyway, e.g. see our discussion with Michael: -https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/ +https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/ All these issues are more or less "theoretical" as there's no real CPU hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by @@ -211,3 +211,9 @@ Thanks for looking into this! -- Vitaly + + +_______________________________________________ +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 9912604..9b9fd74 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,9 +3,44 @@ "ref\087mt98qfi2.fsf@ovpn-194-252.brq.redhat.com\0" "ref\0Y22nrQ7aziK0NMOE@google.com\0" "From\0Vitaly Kuznetsov <vkuznets@redhat.com>\0" - "Subject\0[PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" + "Subject\0Re: [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" "Date\0Tue, 15 Nov 2022 10:30:14 +0100\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0James Morse <james.morse@arm.com>" + Alexandru Elisei <alexandru.elisei@arm.com> + Suzuki K Poulose <suzuki.poulose@arm.com> + Oliver Upton <oliver.upton@linux.dev> + Atish Patra <atishp@atishpatra.org> + David Hildenbrand <david@redhat.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + kvmarm@lists.cs.columbia.edu + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-s390@vger.kernel.org + linux-kernel@vger.kernel.org + Isaku Yamahata <isaku.yamahata@intel.com> + Fabiano Rosas <farosas@linux.ibm.com> + Michael Ellerman <mpe@ellerman.id.au> + Chao Gao <chao.gao@intel.com> + Thomas Gleixner <tglx@linutronix.de> + Yuan Yao <yuan.yao@intel.com> + Paolo Bonzini <pbonzini@redhat.com> + Marc Zyngier <maz@kernel.org> + Huacai Chen <chenhuacai@kernel.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Christian Borntraeger <borntraeger@linux.ibm.com> + Janosch Frank <frankja@linux.ibm.com> + Claudio Imbrenda <imbrenda@linux.ibm.com> + Matthew Rosato <mjrosato@linux.ibm.com> + " Eric Farman <farman@linux.ibm.com>\0" "\00:1\0" "b\0" "Sean Christopherson <seanjc@google.com> writes:\n" @@ -86,7 +121,7 @@ "It seems we can't get away without a dedicated stage for Hyper-V anyway,\n" "e.g. see our discussion with Michael:\n" "\n" - "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/\n" + "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/\n" "\n" "All these issues are more or less \"theoretical\" as there's no real CPU\n" "hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by\n" @@ -220,6 +255,12 @@ "> base-commit: 5f47ba6894477dfbdc5416467a25fb7acb47d404\n" "\n" "-- \n" - Vitaly + "Vitaly\n" + "\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -91596a555581c66f9035665e010006c9886d44491fcc7adb3cc34d005d3aa7ad +1ba9b8eec89be742bbd51aef336491a0d239be729a9a58527c8b7c5e85ecc1d9
diff --git a/a/1.txt b/N4/1.txt index 079f3f3..7a53541 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -76,7 +76,7 @@ Sean Christopherson <seanjc@google.com> writes: It seems we can't get away without a dedicated stage for Hyper-V anyway, e.g. see our discussion with Michael: -https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/ +https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/ All these issues are more or less "theoretical" as there's no real CPU hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by diff --git a/a/content_digest b/N4/content_digest index 9912604..01d6e0c 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -3,9 +3,43 @@ "ref\087mt98qfi2.fsf@ovpn-194-252.brq.redhat.com\0" "ref\0Y22nrQ7aziK0NMOE@google.com\0" "From\0Vitaly Kuznetsov <vkuznets@redhat.com>\0" - "Subject\0[PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" + "Subject\0Re: [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" "Date\0Tue, 15 Nov 2022 10:30:14 +0100\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0kvm@vger.kernel.org" + David Hildenbrand <david@redhat.com> + Atish Patra <atishp@atishpatra.org> + linux-kernel@vger.kernel.org + linux-riscv@lists.infradead.org + Claudio Imbrenda <imbrenda@linux.ibm.com> + kvmarm@lists.cs.columbia.edu + linux-s390@vger.kernel.org + Janosch Frank <frankja@linux.ibm.com> + Huacai Chen <chenhuacai@kernel.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + Palmer Dabbelt <palmer@dabbelt.com> + Christian Borntraeger <borntraeger@linux.ibm.com> + Matthew Rosato <mjrosato@linux.ibm.com> + Chao Gao <chao.gao@intel.com> + Eric Farman <farman@linux.ibm.com> + Albert Ou <aou@eecs.berkeley.edu> + Suzuki K Poulose <suzuki.poulose@arm.com> + Paul Walmsley <paul.walmsley@sifive.com> + Yuan Yao <yuan.yao@intel.com> + kvmarm@lists.linux.dev + Thomas Gleixner <tglx@linutronix.de> + Alexandru Elisei <alexandru.elisei@arm.com> + linux-arm-kernel@lists.infradead.org + Isaku Yamahata <isaku.yamahata@intel.com> + Fabiano Rosas <farosas@linux.ibm.com> + Anup Patel <anup@brainfault.o rg> + linux-mips@vger.kernel.org + Oliver Upton <oliver.upton@linux.dev> + James Morse <james.morse@arm.com> + kvm-riscv@lists.infradead.org + Marc Zyngier <maz@kernel.org> + Paolo Bonzini <pbonzini@redhat.com> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "Sean Christopherson <seanjc@google.com> writes:\n" @@ -86,7 +120,7 @@ "It seems we can't get away without a dedicated stage for Hyper-V anyway,\n" "e.g. see our discussion with Michael:\n" "\n" - "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/\n" + "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/\n" "\n" "All these issues are more or less \"theoretical\" as there's no real CPU\n" "hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by\n" @@ -222,4 +256,4 @@ "-- \n" Vitaly -91596a555581c66f9035665e010006c9886d44491fcc7adb3cc34d005d3aa7ad +42ec557dc45c9b3317e1edbf781642e2ba47d0da0759b8302a87f3bd12f9b2f3
diff --git a/a/1.txt b/N5/1.txt index 079f3f3..bc487a0 100644 --- a/a/1.txt +++ b/N5/1.txt @@ -76,7 +76,7 @@ Sean Christopherson <seanjc@google.com> writes: It seems we can't get away without a dedicated stage for Hyper-V anyway, e.g. see our discussion with Michael: -https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/ +https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/ All these issues are more or less "theoretical" as there's no real CPU hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by @@ -211,3 +211,9 @@ Thanks for looking into this! -- Vitaly + + +_______________________________________________ +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/N5/content_digest index 9912604..74791ab 100644 --- a/a/content_digest +++ b/N5/content_digest @@ -3,9 +3,44 @@ "ref\087mt98qfi2.fsf@ovpn-194-252.brq.redhat.com\0" "ref\0Y22nrQ7aziK0NMOE@google.com\0" "From\0Vitaly Kuznetsov <vkuznets@redhat.com>\0" - "Subject\0[PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" + "Subject\0Re: [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails\0" "Date\0Tue, 15 Nov 2022 10:30:14 +0100\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0James Morse <james.morse@arm.com>" + Alexandru Elisei <alexandru.elisei@arm.com> + Suzuki K Poulose <suzuki.poulose@arm.com> + Oliver Upton <oliver.upton@linux.dev> + Atish Patra <atishp@atishpatra.org> + David Hildenbrand <david@redhat.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + kvmarm@lists.cs.columbia.edu + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-s390@vger.kernel.org + linux-kernel@vger.kernel.org + Isaku Yamahata <isaku.yamahata@intel.com> + Fabiano Rosas <farosas@linux.ibm.com> + Michael Ellerman <mpe@ellerman.id.au> + Chao Gao <chao.gao@intel.com> + Thomas Gleixner <tglx@linutronix.de> + Yuan Yao <yuan.yao@intel.com> + Paolo Bonzini <pbonzini@redhat.com> + Marc Zyngier <maz@kernel.org> + Huacai Chen <chenhuacai@kernel.org> + Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Christian Borntraeger <borntraeger@linux.ibm.com> + Janosch Frank <frankja@linux.ibm.com> + Claudio Imbrenda <imbrenda@linux.ibm.com> + Matthew Rosato <mjrosato@linux.ibm.com> + " Eric Farman <farman@linux.ibm.com>\0" "\00:1\0" "b\0" "Sean Christopherson <seanjc@google.com> writes:\n" @@ -86,7 +121,7 @@ "It seems we can't get away without a dedicated stage for Hyper-V anyway,\n" "e.g. see our discussion with Michael:\n" "\n" - "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf at ovpn-192-136.brq.redhat.com/\n" + "https://lore.kernel.org/linux-hyperv/878rkqr7ku.fsf@ovpn-192-136.brq.redhat.com/\n" "\n" "All these issues are more or less \"theoretical\" as there's no real CPU\n" "hotplug on Hyper-V/Azure. Yes, it is possible to trigger problems by\n" @@ -220,6 +255,12 @@ "> base-commit: 5f47ba6894477dfbdc5416467a25fb7acb47d404\n" "\n" "-- \n" - Vitaly + "Vitaly\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 -91596a555581c66f9035665e010006c9886d44491fcc7adb3cc34d005d3aa7ad +c85ea574be8fc7507ac9bf018dd94cbd2ab2b31eb9d590b6f4a4b829d0e24bbe
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.