diff for duplicates of <Y3UHOg7E0iRFpjml@google.com> diff --git a/a/1.txt b/N1/1.txt index 30fb74f..0e4b953 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -60,3 +60,7 @@ break KVM). > patch? Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. +_______________________________________________ +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 11ed053..f6890c0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,9 +2,44 @@ "ref\020221102231911.3107438-14-seanjc@google.com\0" "ref\0e8e3b4c7bf3bd733c626618b57f9bf2f1835770e.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" + "Subject\0Re: [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" "Date\0Wed, 16 Nov 2022 15:52:26 +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> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + 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> + mpe@ellerman.id.au <mpe@ellerman.id.au> + 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> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + 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> + atishp@atishpatra.org <atishp@atishpatra.org> + 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> + maz@kernel.org <maz@kernel.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 Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -68,6 +103,10 @@ "> Also, do you also want to update Documentation/virt/kvm/locking.rst\" in this\n" "> patch?\n" "\n" - Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. + "Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used.\n" + "_______________________________________________\n" + "kvmarm mailing list\n" + "kvmarm@lists.cs.columbia.edu\n" + https://lists.cs.columbia.edu/mailman/listinfo/kvmarm -eee8bcb27ead3481d3471b60da6c9e128a99820ab613a1b21ec8f000468688de +8fc194fc019684311f1b713d77abb56797f447b34dccf88082bc6121e8dbfb10
diff --git a/a/content_digest b/N2/content_digest index 11ed053..a73f111 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,9 +2,49 @@ "ref\020221102231911.3107438-14-seanjc@google.com\0" "ref\0e8e3b4c7bf3bd733c626618b57f9bf2f1835770e.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" + "Subject\0Re: [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" "Date\0Wed, 16 Nov 2022 15:52:26 +0000\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Huang" + " Kai <kai.huang@intel.com>\0" + "Cc\0imbrenda@linux.ibm.com <imbrenda@linux.ibm.com>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + mjrosato@linux.ibm.com <mjrosato@linux.ibm.com> + vkuznets@redhat.com <vkuznets@redhat.com> + farman@linux.ibm.com <farman@linux.ibm.com> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + anup@brainfault.org <anup@brainfault.org> + pbonzini@redhat.com <pbonzini@redhat.com> + borntraeger@linux.ibm.com <borntraeger@linux.ibm.com> + aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + frankja@linux.ibm.com <frankja@linux.ibm.com> + oliver.upton@linux.dev <oliver.upton@linux.dev> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Yao + Yuan <yuan.yao@intel.com> + farosas@linux.ibm.com <farosas@linux.ibm.com> + david@redhat.com <david@redhat.com> + james.morse@arm.com <james.morse@arm.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + alexandru.elisei@arm.com <alexandru.elisei@arm.com> + linux-s390@vger.kernel.org <linux-s390@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + tglx@linutronix.de <tglx@linutronix.de> + Yamahata + Isaku <isaku.yamahata@intel.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + suzuki.poulose@arm.com <suzuki.poulose@arm.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + Gao + Chao <chao.gao@intel.com> + atishp@atishpatra.org <atishp@atishpatra.org> + " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0" "\00:1\0" "b\0" "On Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -70,4 +110,4 @@ "\n" Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. -eee8bcb27ead3481d3471b60da6c9e128a99820ab613a1b21ec8f000468688de +b3b86c908afd71fd6e55496d82164f9bf70544bf32aebd1cdcdcc128d89f8914
diff --git a/a/1.txt b/N3/1.txt index 30fb74f..1618177 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -60,3 +60,8 @@ break KVM). > patch? Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. + +_______________________________________________ +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 11ed053..d7bf11f 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,9 +2,49 @@ "ref\020221102231911.3107438-14-seanjc@google.com\0" "ref\0e8e3b4c7bf3bd733c626618b57f9bf2f1835770e.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" + "Subject\0Re: [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" "Date\0Wed, 16 Nov 2022 15:52:26 +0000\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Huang" + " Kai <kai.huang@intel.com>\0" + "Cc\0imbrenda@linux.ibm.com <imbrenda@linux.ibm.com>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + mjrosato@linux.ibm.com <mjrosato@linux.ibm.com> + vkuznets@redhat.com <vkuznets@redhat.com> + farman@linux.ibm.com <farman@linux.ibm.com> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + anup@brainfault.org <anup@brainfault.org> + pbonzini@redhat.com <pbonzini@redhat.com> + borntraeger@linux.ibm.com <borntraeger@linux.ibm.com> + aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + frankja@linux.ibm.com <frankja@linux.ibm.com> + oliver.upton@linux.dev <oliver.upton@linux.dev> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Yao + Yuan <yuan.yao@intel.com> + farosas@linux.ibm.com <farosas@linux.ibm.com> + david@redhat.com <david@redhat.com> + james.morse@arm.com <james.morse@arm.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + alexandru.elisei@arm.com <alexandru.elisei@arm.com> + linux-s390@vger.kernel.org <linux-s390@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + tglx@linutronix.de <tglx@linutronix.de> + Yamahata + Isaku <isaku.yamahata@intel.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + suzuki.poulose@arm.com <suzuki.poulose@arm.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + Gao + Chao <chao.gao@intel.com> + atishp@atishpatra.org <atishp@atishpatra.org> + " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0" "\00:1\0" "b\0" "On Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -68,6 +108,11 @@ "> Also, do you also want to update Documentation/virt/kvm/locking.rst\" in this\n" "> patch?\n" "\n" - Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. + "Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -eee8bcb27ead3481d3471b60da6c9e128a99820ab613a1b21ec8f000468688de +533c9fc40706a0188b5f7371125bb84332cab0564b3d77c4d120b44cd2d1acd9
diff --git a/a/content_digest b/N4/content_digest index 11ed053..b8753d0 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -2,9 +2,48 @@ "ref\020221102231911.3107438-14-seanjc@google.com\0" "ref\0e8e3b4c7bf3bd733c626618b57f9bf2f1835770e.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" + "Subject\0Re: [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" "Date\0Wed, 16 Nov 2022 15:52:26 +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> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + 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> + chenhuacai@kernel.org <chenhuacai@kernel.org> + aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + james.morse@arm.com <james.morse@arm.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> + suzuki.poulose@arm.com <suzuki.poulose@arm.com> + kvm@vger.kernel.org <kvm@vger.kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + kvmarm@lists.linux .dev <kvmarm@lists.linux.dev> + tglx@linutronix.de <tglx@linutronix.de> + alexandru.elisei@arm.com <alexandru.elisei@arm.com> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + Yamahata + Isaku <isaku.yamahata@intel.com> + atishp@atishpatra.org <atishp@atishpatra.org> + farosas@linux.ibm.com <farosas@linux.ibm.com> + anup@brainfault.org <anup@brainfault.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + oliver.upton@linux.dev <oliver.upton@linux.dev> + palmer@dabbelt.com <palmer@dabbelt.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + maz@kernel.org <maz@kernel.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 Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -70,4 +109,4 @@ "\n" Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. -eee8bcb27ead3481d3471b60da6c9e128a99820ab613a1b21ec8f000468688de +a6b6b3300518e6336d5971abcb7aadfe5eb9349249ef1206ec4f6ec05a748180
diff --git a/a/1.txt b/N5/1.txt index 30fb74f..bbba9f7 100644 --- a/a/1.txt +++ b/N5/1.txt @@ -60,3 +60,8 @@ break KVM). > patch? Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. + +_______________________________________________ +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 11ed053..00d7c6a 100644 --- a/a/content_digest +++ b/N5/content_digest @@ -2,9 +2,49 @@ "ref\020221102231911.3107438-14-seanjc@google.com\0" "ref\0e8e3b4c7bf3bd733c626618b57f9bf2f1835770e.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" + "Subject\0Re: [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)\0" "Date\0Wed, 16 Nov 2022 15:52:26 +0000\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Huang" + " Kai <kai.huang@intel.com>\0" + "Cc\0imbrenda@linux.ibm.com <imbrenda@linux.ibm.com>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + mjrosato@linux.ibm.com <mjrosato@linux.ibm.com> + vkuznets@redhat.com <vkuznets@redhat.com> + farman@linux.ibm.com <farman@linux.ibm.com> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + anup@brainfault.org <anup@brainfault.org> + pbonzini@redhat.com <pbonzini@redhat.com> + borntraeger@linux.ibm.com <borntraeger@linux.ibm.com> + aleksandar.qemu.devel@gmail.com <aleksandar.qemu.devel@gmail.com> + frankja@linux.ibm.com <frankja@linux.ibm.com> + oliver.upton@linux.dev <oliver.upton@linux.dev> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Yao + Yuan <yuan.yao@intel.com> + farosas@linux.ibm.com <farosas@linux.ibm.com> + david@redhat.com <david@redhat.com> + james.morse@arm.com <james.morse@arm.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + alexandru.elisei@arm.com <alexandru.elisei@arm.com> + linux-s390@vger.kernel.org <linux-s390@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + tglx@linutronix.de <tglx@linutronix.de> + Yamahata + Isaku <isaku.yamahata@intel.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + suzuki.poulose@arm.com <suzuki.poulose@arm.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu> + Gao + Chao <chao.gao@intel.com> + atishp@atishpatra.org <atishp@atishpatra.org> + " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0" "\00:1\0" "b\0" "On Wed, Nov 16, 2022, Huang, Kai wrote:\n" @@ -68,6 +108,11 @@ "> Also, do you also want to update Documentation/virt/kvm/locking.rst\" in this\n" "> patch?\n" "\n" - Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used. + "Hmm, yeah. That'd also be a good place to document why kvm_lock isn't used.\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 -eee8bcb27ead3481d3471b60da6c9e128a99820ab613a1b21ec8f000468688de +1ceea84574c779bbdb29f161c827b396ea6a5930fb92946fd2f0ed545e90ab7b
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.