diff for duplicates of <ZQNbDt6vqwC4gZmi@google.com> diff --git a/a/content_digest b/N1/content_digest index 1201ff6..1f39558 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,49 @@ "ref\0diqzttsiu67n.fsf@ackerleytng-ctop.c.googlers.com\0" "ref\0253965df-6d80-bbfd-ab01-f9e69b274bf3@quicinc.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 12:12:14 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Elliot Berman <quic_eberman@quicinc.com>\0" + "Cc\0Ackerley Tng <ackerleytng@google.com>" + pbonzini@redhat.com + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 28, 2023, Elliot Berman wrote:\n" @@ -48,4 +88,4 @@ "userspace, and that just doesn't mesh well with CoW'd memory being shared across\n" multiple VMs. -2c496116bd963a06d97eb18c0de3bf8dd677b9d4a0367cfc26ef7658dc2fab24 +37c27401828d3386326b3a64468cb3e1276c27b5516cab2e0cd3cdcf30be5377
diff --git a/a/1.txt b/N2/1.txt index 0aff26f..7a38da9 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -39,3 +39,8 @@ But I highly doubt we'll ever do that, because one of core tenets of KVM+gmem is to isolate guest memory from the rest of the world, and especially from host userspace, and that just doesn't mesh well with CoW'd memory being shared across multiple VMs. + +_______________________________________________ +linux-riscv mailing list +linux-riscv@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-riscv diff --git a/a/content_digest b/N2/content_digest index 1201ff6..23641cc 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,9 +1,49 @@ "ref\0diqzttsiu67n.fsf@ackerleytng-ctop.c.googlers.com\0" "ref\0253965df-6d80-bbfd-ab01-f9e69b274bf3@quicinc.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 12:12:14 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Elliot Berman <quic_eberman@quicinc.com>\0" + "Cc\0Ackerley Tng <ackerleytng@google.com>" + pbonzini@redhat.com + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 28, 2023, Elliot Berman wrote:\n" @@ -46,6 +86,11 @@ "But I highly doubt we'll ever do that, because one of core tenets of KVM+gmem is\n" "to isolate guest memory from the rest of the world, and especially from host\n" "userspace, and that just doesn't mesh well with CoW'd memory being shared across\n" - multiple VMs. + "multiple VMs.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -2c496116bd963a06d97eb18c0de3bf8dd677b9d4a0367cfc26ef7658dc2fab24 +c6600558a0425c142b56dc4f61d7f37d3707cbb0d5638229bd03ed396cf4bc96
diff --git a/a/content_digest b/N3/content_digest index 1201ff6..da52ee4 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,9 +1,48 @@ "ref\0diqzttsiu67n.fsf@ackerleytng-ctop.c.googlers.com\0" "ref\0253965df-6d80-bbfd-ab01-f9e69b274bf3@quicinc.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 12:12:14 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Elliot Berman <quic_eberman@quicinc.com>\0" + "Cc\0kvm@vger.kernel.org" + david@redhat.com + yu.c.zhang@linux.intel.com + linux-kernel@vger.kernel.org + linux-mm@kvack.org + chao.p.peng@linux.intel.com + linux-riscv@lists.infradead.org + isaku.yamahata@gmail.com + paul@paul-moore.com + maz@kernel.org + chenhuacai@kernel.org + jmorris@namei.org + willy@infradead.org + wei.w.wang@intel.com + tabba@google.com + jarkko@kernel.org + serge@hallyn.com + mail@maciej.szmigiero.name + aou@eecs.berkeley.edu + vbabka@suse.cz + michael.roth@amd.com + Ackerley Tng <ackerleytng@google.com> + paul.walmsley@sifive.com + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + qperret@google.com + liam.merwick@oracle.com + linux-mips@vger.kernel.org + oliver.upton@linux.dev + linux-security-module@vger.kernel.org + palmer@dabbelt.com + kvm-riscv@lists.infradead.org + anup@brainfault.org + linux-fsdevel@vger.kernel.org + pbonzini@redhat.com + akpm@linux-foundation.org + vannapurve@google.com + linuxppc-dev@lists.ozlabs.org + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 28, 2023, Elliot Berman wrote:\n" @@ -48,4 +87,4 @@ "userspace, and that just doesn't mesh well with CoW'd memory being shared across\n" multiple VMs. -2c496116bd963a06d97eb18c0de3bf8dd677b9d4a0367cfc26ef7658dc2fab24 +8ab654a42b4dea92f1fb547f7c660ef9163cf1237ee7a61160a7f2b28ed004f1
diff --git a/a/1.txt b/N4/1.txt index 0aff26f..f2be1ed 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -39,3 +39,8 @@ But I highly doubt we'll ever do that, because one of core tenets of KVM+gmem is to isolate guest memory from the rest of the world, and especially from host userspace, and that just doesn't mesh well with CoW'd memory being shared across multiple VMs. + +_______________________________________________ +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 1201ff6..b98cc17 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -1,9 +1,49 @@ "ref\0diqzttsiu67n.fsf@ackerleytng-ctop.c.googlers.com\0" "ref\0253965df-6d80-bbfd-ab01-f9e69b274bf3@quicinc.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 12:12:14 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Elliot Berman <quic_eberman@quicinc.com>\0" + "Cc\0Ackerley Tng <ackerleytng@google.com>" + pbonzini@redhat.com + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 28, 2023, Elliot Berman wrote:\n" @@ -46,6 +86,11 @@ "But I highly doubt we'll ever do that, because one of core tenets of KVM+gmem is\n" "to isolate guest memory from the rest of the world, and especially from host\n" "userspace, and that just doesn't mesh well with CoW'd memory being shared across\n" - multiple VMs. + "multiple VMs.\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 -2c496116bd963a06d97eb18c0de3bf8dd677b9d4a0367cfc26ef7658dc2fab24 +582cf013a07ea99619c921087b48d13f7b9a52d6a632af1b5cdb32e9c55d832c
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.