diff for duplicates of <ZNZza/emWldkJC6X@google.com> diff --git a/a/1.txt b/N1/1.txt index 3c16792..f9bbf0a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Thu, Aug 10, 2023, Vishal Annapurve wrote: -> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote: +> On Tue, Aug 8, 2023 at 2:13 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > > > > + When binding a memslot to the file, if a kvm pointer exists, it must diff --git a/a/content_digest b/N1/content_digest index 577182c..0da879b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,13 +3,52 @@ "ref\0ZNKv9ul2I7A4V7IF@google.com\0" "ref\0CAGtprH9YE50RtqhW-U+wK0Vv6aKfqqtOPn8q4s8or=UZwPXZoA@mail.gmail.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\0Fri, 11 Aug 2023 10:44:11 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Vishal Annapurve <vannapurve@google.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 + 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 Thu, Aug 10, 2023, Vishal Annapurve wrote:\n" - "> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Tue, Aug 8, 2023 at 2:13\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > ...\n" "> \n" "> > > + When binding a memslot to the file, if a kvm pointer exists, it must\n" @@ -64,4 +103,4 @@ "if that use case is nonsensical for confidential VMs (and it probably is nonsensical),\n" I don't want to define KVM's ABI based on what we *think* userspace will do. -2eba1803c76221e903afee92fe71c80d6a89f2a8ba7e6d2c8e5ce8839ed09966 +16426353ebb647ea583b7261b0868b2c1884987e23ec451e05e9bd248917f8fb
diff --git a/a/1.txt b/N2/1.txt index 3c16792..1ac081e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On Thu, Aug 10, 2023, Vishal Annapurve wrote: -> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote: +> On Tue, Aug 8, 2023 at 2:13 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > > > > + When binding a memslot to the file, if a kvm pointer exists, it must @@ -53,3 +53,8 @@ There are no guarantees that the host will reclaim the memory. E.g. QEMU will delete and re-create memslots for "regular" VMs when emulating option ROMs. Even if that use case is nonsensical for confidential VMs (and it probably is nonsensical), I don't want to define KVM's ABI based on what we *think* userspace will do. + +_______________________________________________ +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 577182c..50a4e52 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,13 +3,52 @@ "ref\0ZNKv9ul2I7A4V7IF@google.com\0" "ref\0CAGtprH9YE50RtqhW-U+wK0Vv6aKfqqtOPn8q4s8or=UZwPXZoA@mail.gmail.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\0Fri, 11 Aug 2023 10:44:11 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Vishal Annapurve <vannapurve@google.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 + 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 Thu, Aug 10, 2023, Vishal Annapurve wrote:\n" - "> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Tue, Aug 8, 2023 at 2:13\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > ...\n" "> \n" "> > > + When binding a memslot to the file, if a kvm pointer exists, it must\n" @@ -62,6 +101,11 @@ "There are no guarantees that the host will reclaim the memory. E.g. QEMU will\n" "delete and re-create memslots for \"regular\" VMs when emulating option ROMs. Even\n" "if that use case is nonsensical for confidential VMs (and it probably is nonsensical),\n" - I don't want to define KVM's ABI based on what we *think* userspace will do. + "I don't want to define KVM's ABI based on what we *think* userspace will do.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -2eba1803c76221e903afee92fe71c80d6a89f2a8ba7e6d2c8e5ce8839ed09966 +00d4346c08d868419e1b8f8a64678f90272e90d642dcf34e634ece42a4c034c9
diff --git a/a/1.txt b/N3/1.txt index 3c16792..f9bbf0a 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,5 +1,5 @@ On Thu, Aug 10, 2023, Vishal Annapurve wrote: -> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote: +> On Tue, Aug 8, 2023 at 2:13 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > > > > + When binding a memslot to the file, if a kvm pointer exists, it must diff --git a/a/content_digest b/N3/content_digest index 577182c..4c10737 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,13 +3,51 @@ "ref\0ZNKv9ul2I7A4V7IF@google.com\0" "ref\0CAGtprH9YE50RtqhW-U+wK0Vv6aKfqqtOPn8q4s8or=UZwPXZoA@mail.gmail.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\0Fri, 11 Aug 2023 10:44:11 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Vishal Annapurve <vannapurve@google.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 + linuxppc-dev@lists.ozlabs.org + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Thu, Aug 10, 2023, Vishal Annapurve wrote:\n" - "> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Tue, Aug 8, 2023 at 2:13\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > ...\n" "> \n" "> > > + When binding a memslot to the file, if a kvm pointer exists, it must\n" @@ -64,4 +102,4 @@ "if that use case is nonsensical for confidential VMs (and it probably is nonsensical),\n" I don't want to define KVM's ABI based on what we *think* userspace will do. -2eba1803c76221e903afee92fe71c80d6a89f2a8ba7e6d2c8e5ce8839ed09966 +6d76341e0519f4169e4057d50a4b79f5d5cfd3e8c84b6d90d681a7882ed47976
diff --git a/a/1.txt b/N4/1.txt index 3c16792..5d61d8f 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -1,5 +1,5 @@ On Thu, Aug 10, 2023, Vishal Annapurve wrote: -> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote: +> On Tue, Aug 8, 2023 at 2:13 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > > > > + When binding a memslot to the file, if a kvm pointer exists, it must @@ -53,3 +53,8 @@ There are no guarantees that the host will reclaim the memory. E.g. QEMU will delete and re-create memslots for "regular" VMs when emulating option ROMs. Even if that use case is nonsensical for confidential VMs (and it probably is nonsensical), I don't want to define KVM's ABI based on what we *think* userspace will do. + +_______________________________________________ +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 577182c..d9a5d79 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -3,13 +3,52 @@ "ref\0ZNKv9ul2I7A4V7IF@google.com\0" "ref\0CAGtprH9YE50RtqhW-U+wK0Vv6aKfqqtOPn8q4s8or=UZwPXZoA@mail.gmail.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\0Fri, 11 Aug 2023 10:44:11 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Vishal Annapurve <vannapurve@google.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 + 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 Thu, Aug 10, 2023, Vishal Annapurve wrote:\n" - "> On Tue, Aug 8, 2023 at 2:13?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Tue, Aug 8, 2023 at 2:13\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > ...\n" "> \n" "> > > + When binding a memslot to the file, if a kvm pointer exists, it must\n" @@ -62,6 +101,11 @@ "There are no guarantees that the host will reclaim the memory. E.g. QEMU will\n" "delete and re-create memslots for \"regular\" VMs when emulating option ROMs. Even\n" "if that use case is nonsensical for confidential VMs (and it probably is nonsensical),\n" - I don't want to define KVM's ABI based on what we *think* userspace will do. + "I don't want to define KVM's ABI based on what we *think* userspace will do.\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 -2eba1803c76221e903afee92fe71c80d6a89f2a8ba7e6d2c8e5ce8839ed09966 +9031a7bade38cb05cfbcb725b1d9d140b7b98a82a22cdb9aead2f21d8b47a916
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.