diff for duplicates of <ZUFGRyQEuWj4RJS0@google.com> diff --git a/a/1.txt b/N1/1.txt index b86fcd1..8aaca1c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -11,10 +11,10 @@ On 2023-10-27 11:21 AM, Sean Christopherson wrote: > being writable in host userspace, as KVM's ABI uses VMA protections to > define the allow guest protection. Userspace can fudge this by > establishing two mappings, a writable mapping for the guest and readable -> one for itself, but that?s suboptimal on multiple fronts. +> one for itself, but that’s suboptimal on multiple fronts. > > Similarly, KVM currently requires the guest mapping size to be a strict -> subset of the host userspace mapping size, e.g. KVM doesn?t support +> subset of the host userspace mapping size, e.g. KVM doesn’t support > creating a 1GiB guest mapping unless userspace also has a 1GiB guest > mapping. Decoupling the mappings sizes would allow userspace to precisely > map only what is needed without impacting guest performance, e.g. to diff --git a/a/content_digest b/N1/content_digest index e3c6c74..00a9695 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,52 @@ "ref\020231027182217.3615211-1-seanjc@google.com\0" "ref\020231027182217.3615211-17-seanjc@google.com\0" "From\0David Matlack <dmatlack@google.com>\0" - "Subject\0[PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Tue, 31 Oct 2023 11:24:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Alexander Viro <viro@zeniv.linux.org.uk> + Christian Brauner <brauner@kernel.org> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + 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-kernel@vger.kernel.org + Xiaoyao Li <xiaoyao.li@intel.com> + Xu Yilun <yilun.xu@intel.com> + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + Yu Zhang <yu.c.zhang@linux.intel.com> + Isaku Yamahata <isaku.yamahata@intel.com> + " Micka\303\253l Sala\303\274n <mic@digikod.net>" + Vlastimil Babka <vbabka@suse.cz> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On 2023-10-27 11:21 AM, Sean Christopherson wrote:\n" @@ -19,10 +62,10 @@ "> being writable in host userspace, as KVM's ABI uses VMA protections to\n" "> define the allow guest protection. Userspace can fudge this by\n" "> establishing two mappings, a writable mapping for the guest and readable\n" - "> one for itself, but that?s suboptimal on multiple fronts.\n" + "> one for itself, but that\342\200\231s suboptimal on multiple fronts.\n" "> \n" "> Similarly, KVM currently requires the guest mapping size to be a strict\n" - "> subset of the host userspace mapping size, e.g. KVM doesn?t support\n" + "> subset of the host userspace mapping size, e.g. KVM doesn\342\200\231t support\n" "> creating a 1GiB guest mapping unless userspace also has a 1GiB guest\n" "> mapping. Decoupling the mappings sizes would allow userspace to precisely\n" "> map only what is needed without impacting guest performance, e.g. to\n" @@ -58,4 +101,4 @@ "Maybe can you sketch out how you see this proposal being extensible to\n" using guest_memfd for shared mappings? -1f9c083032428be7bac94365edc9922c2b2d70941f7d7b7d494544a9823ad1db +fe77821e47a851178d8876d333bac55d42bb4270a4ac6cbc22075d92e4e6a10f
diff --git a/a/1.txt b/N2/1.txt index b86fcd1..7bb4d09 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -11,10 +11,10 @@ On 2023-10-27 11:21 AM, Sean Christopherson wrote: > being writable in host userspace, as KVM's ABI uses VMA protections to > define the allow guest protection. Userspace can fudge this by > establishing two mappings, a writable mapping for the guest and readable -> one for itself, but that?s suboptimal on multiple fronts. +> one for itself, but that’s suboptimal on multiple fronts. > > Similarly, KVM currently requires the guest mapping size to be a strict -> subset of the host userspace mapping size, e.g. KVM doesn?t support +> subset of the host userspace mapping size, e.g. KVM doesn’t support > creating a 1GiB guest mapping unless userspace also has a 1GiB guest > mapping. Decoupling the mappings sizes would allow userspace to precisely > map only what is needed without impacting guest performance, e.g. to @@ -49,3 +49,8 @@ attributes work with "legacy" HVA-based memslots. Maybe can you sketch out how you see this proposal being extensible to using guest_memfd for shared mappings? + +_______________________________________________ +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 e3c6c74..5a90402 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,9 +1,52 @@ "ref\020231027182217.3615211-1-seanjc@google.com\0" "ref\020231027182217.3615211-17-seanjc@google.com\0" "From\0David Matlack <dmatlack@google.com>\0" - "Subject\0[PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Tue, 31 Oct 2023 11:24:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Alexander Viro <viro@zeniv.linux.org.uk> + Christian Brauner <brauner@kernel.org> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + 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-kernel@vger.kernel.org + Xiaoyao Li <xiaoyao.li@intel.com> + Xu Yilun <yilun.xu@intel.com> + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + Yu Zhang <yu.c.zhang@linux.intel.com> + Isaku Yamahata <isaku.yamahata@intel.com> + " Micka\303\253l Sala\303\274n <mic@digikod.net>" + Vlastimil Babka <vbabka@suse.cz> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On 2023-10-27 11:21 AM, Sean Christopherson wrote:\n" @@ -19,10 +62,10 @@ "> being writable in host userspace, as KVM's ABI uses VMA protections to\n" "> define the allow guest protection. Userspace can fudge this by\n" "> establishing two mappings, a writable mapping for the guest and readable\n" - "> one for itself, but that?s suboptimal on multiple fronts.\n" + "> one for itself, but that\342\200\231s suboptimal on multiple fronts.\n" "> \n" "> Similarly, KVM currently requires the guest mapping size to be a strict\n" - "> subset of the host userspace mapping size, e.g. KVM doesn?t support\n" + "> subset of the host userspace mapping size, e.g. KVM doesn\342\200\231t support\n" "> creating a 1GiB guest mapping unless userspace also has a 1GiB guest\n" "> mapping. Decoupling the mappings sizes would allow userspace to precisely\n" "> map only what is needed without impacting guest performance, e.g. to\n" @@ -56,6 +99,11 @@ "attributes work with \"legacy\" HVA-based memslots.\n" "\n" "Maybe can you sketch out how you see this proposal being extensible to\n" - using guest_memfd for shared mappings? + "using guest_memfd for shared mappings?\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -1f9c083032428be7bac94365edc9922c2b2d70941f7d7b7d494544a9823ad1db +c4982825a3ebcc61566575ff6de7c690bea7c8a87996c5a837a34cfa5e68c03f
diff --git a/a/1.txt b/N3/1.txt index b86fcd1..8aaca1c 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -11,10 +11,10 @@ On 2023-10-27 11:21 AM, Sean Christopherson wrote: > being writable in host userspace, as KVM's ABI uses VMA protections to > define the allow guest protection. Userspace can fudge this by > establishing two mappings, a writable mapping for the guest and readable -> one for itself, but that?s suboptimal on multiple fronts. +> one for itself, but that’s suboptimal on multiple fronts. > > Similarly, KVM currently requires the guest mapping size to be a strict -> subset of the host userspace mapping size, e.g. KVM doesn?t support +> subset of the host userspace mapping size, e.g. KVM doesn’t support > creating a 1GiB guest mapping unless userspace also has a 1GiB guest > mapping. Decoupling the mappings sizes would allow userspace to precisely > map only what is needed without impacting guest performance, e.g. to diff --git a/a/content_digest b/N3/content_digest index e3c6c74..10d4f8c 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,9 +1,51 @@ "ref\020231027182217.3615211-1-seanjc@google.com\0" "ref\020231027182217.3615211-17-seanjc@google.com\0" "From\0David Matlack <dmatlack@google.com>\0" - "Subject\0[PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Tue, 31 Oct 2023 11:24:07 -0700\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> + linux-kernel@vger.kernel.org + linux-mm@kvack.org + Chao Peng <chao.p.peng@linux.intel.com> + linux-riscv@lists.infradead.org + Isaku Yamahata <isaku.yamahata@gmail.com> + Marc Zyngier <maz@kernel.org> + Huacai Chen <chenhuacai@kernel.org> + Xiaoyao Li <xiaoyao.li@intel.com> + Matthew Wilcox (Oracle) <willy@infradead.org> + Wang <wei.w.wang@intel.com> + Fuad Tabba <tabba@google.com> + Yu Zhang <yu.c.zhang@linux.intel.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Albert Ou <aou@eecs.berkeley.edu> + Vlastimil Babka <vbabka@suse.cz> + Michael Roth <michael.roth@amd.com> + Ackerley Tng <ackerleytng@google.com> + Alexander Viro <viro@zeniv.linux.org.uk> + Paul Walmsley <paul.walmsley@sifive.com> + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + " Micka\303\253l Sala\303\274n <mic@digikod.net>" + Isaku Yamahata <isaku.yamahata@intel.com> + Christian Brauner <brauner@kernel.org> + Quentin Perret <qperret@google.com> + Li am Merwick <liam.merwick@oracle.com> + linux-mips@vger.kernel.org + Oliver Upton <oliver.upton@linux.dev> + Jarkko Sakkinen <jarkko@kernel.org> + Palmer Dabbelt <palmer@dabbelt.com> + Kirill A . Shutemov <kirill.shutemov@linux.intel.com> + kvm-riscv@lists.infradead.org + Anup Patel <anup@brainfault.org> + linux-fsdevel@vger.kernel.org + Paolo Bonzini <pbonzini@redhat.com> + Andrew Morton <akpm@linux-foundation.org> + Vishal Annapurve <vannapurve@google.com> + linuxppc-dev@lists.ozlabs.org + Xu Yilun <yilun.xu@intel.com> + " Anish Moorthy <amoorthy@google.com>\0" "\00:1\0" "b\0" "On 2023-10-27 11:21 AM, Sean Christopherson wrote:\n" @@ -19,10 +61,10 @@ "> being writable in host userspace, as KVM's ABI uses VMA protections to\n" "> define the allow guest protection. Userspace can fudge this by\n" "> establishing two mappings, a writable mapping for the guest and readable\n" - "> one for itself, but that?s suboptimal on multiple fronts.\n" + "> one for itself, but that\342\200\231s suboptimal on multiple fronts.\n" "> \n" "> Similarly, KVM currently requires the guest mapping size to be a strict\n" - "> subset of the host userspace mapping size, e.g. KVM doesn?t support\n" + "> subset of the host userspace mapping size, e.g. KVM doesn\342\200\231t support\n" "> creating a 1GiB guest mapping unless userspace also has a 1GiB guest\n" "> mapping. Decoupling the mappings sizes would allow userspace to precisely\n" "> map only what is needed without impacting guest performance, e.g. to\n" @@ -58,4 +100,4 @@ "Maybe can you sketch out how you see this proposal being extensible to\n" using guest_memfd for shared mappings? -1f9c083032428be7bac94365edc9922c2b2d70941f7d7b7d494544a9823ad1db +428b1199137498c5110783162fcf6f03fe0b853c376c99c6c275bfe0aa5e7f5b
diff --git a/a/1.txt b/N4/1.txt index b86fcd1..7059bbe 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -11,10 +11,10 @@ On 2023-10-27 11:21 AM, Sean Christopherson wrote: > being writable in host userspace, as KVM's ABI uses VMA protections to > define the allow guest protection. Userspace can fudge this by > establishing two mappings, a writable mapping for the guest and readable -> one for itself, but that?s suboptimal on multiple fronts. +> one for itself, but that’s suboptimal on multiple fronts. > > Similarly, KVM currently requires the guest mapping size to be a strict -> subset of the host userspace mapping size, e.g. KVM doesn?t support +> subset of the host userspace mapping size, e.g. KVM doesn’t support > creating a 1GiB guest mapping unless userspace also has a 1GiB guest > mapping. Decoupling the mappings sizes would allow userspace to precisely > map only what is needed without impacting guest performance, e.g. to @@ -49,3 +49,8 @@ attributes work with "legacy" HVA-based memslots. Maybe can you sketch out how you see this proposal being extensible to using guest_memfd for shared mappings? + +_______________________________________________ +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 e3c6c74..b80c0ee 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -1,9 +1,52 @@ "ref\020231027182217.3615211-1-seanjc@google.com\0" "ref\020231027182217.3615211-17-seanjc@google.com\0" "From\0David Matlack <dmatlack@google.com>\0" - "Subject\0[PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [PATCH v13 16/35] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Tue, 31 Oct 2023 11:24:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Sean Christopherson <seanjc@google.com>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Alexander Viro <viro@zeniv.linux.org.uk> + Christian Brauner <brauner@kernel.org> + Matthew Wilcox (Oracle) <willy@infradead.org> + Andrew Morton <akpm@linux-foundation.org> + 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-kernel@vger.kernel.org + Xiaoyao Li <xiaoyao.li@intel.com> + Xu Yilun <yilun.xu@intel.com> + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + Yu Zhang <yu.c.zhang@linux.intel.com> + Isaku Yamahata <isaku.yamahata@intel.com> + " Micka\303\253l Sala\303\274n <mic@digikod.net>" + Vlastimil Babka <vbabka@suse.cz> + Vishal Annapurve <vannapurve@google.com> + Ackerley Tng <ackerleytng@google.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + David Hildenbrand <david@redhat.com> + Quentin Perret <qperret@google.com> + Michael Roth <michael.roth@amd.com> + Wang <wei.w.wang@intel.com> + Liam Merwick <liam.merwick@oracle.com> + Isaku Yamahata <isaku.yamahata@gmail.com> + " Kirill A . Shutemov <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On 2023-10-27 11:21 AM, Sean Christopherson wrote:\n" @@ -19,10 +62,10 @@ "> being writable in host userspace, as KVM's ABI uses VMA protections to\n" "> define the allow guest protection. Userspace can fudge this by\n" "> establishing two mappings, a writable mapping for the guest and readable\n" - "> one for itself, but that?s suboptimal on multiple fronts.\n" + "> one for itself, but that\342\200\231s suboptimal on multiple fronts.\n" "> \n" "> Similarly, KVM currently requires the guest mapping size to be a strict\n" - "> subset of the host userspace mapping size, e.g. KVM doesn?t support\n" + "> subset of the host userspace mapping size, e.g. KVM doesn\342\200\231t support\n" "> creating a 1GiB guest mapping unless userspace also has a 1GiB guest\n" "> mapping. Decoupling the mappings sizes would allow userspace to precisely\n" "> map only what is needed without impacting guest performance, e.g. to\n" @@ -56,6 +99,11 @@ "attributes work with \"legacy\" HVA-based memslots.\n" "\n" "Maybe can you sketch out how you see this proposal being extensible to\n" - using guest_memfd for shared mappings? + "using guest_memfd for shared mappings?\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 -1f9c083032428be7bac94365edc9922c2b2d70941f7d7b7d494544a9823ad1db +c05f80e3f2abfabc5f340dd8565bc8dec7d76f7e02cebc513a6eaaa0fcc58aff
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.