diff for duplicates of <ZUF8A5KpwpA6IKUH@google.com> diff --git a/a/1.txt b/N1/1.txt index 75be7e3..36d8211 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Tue, Oct 31, 2023, Fuad Tabba wrote: > Hi, > -> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote: +> On Fri, Oct 27, 2023 at 7:23 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > @@ -81,7 +81,7 @@ Copying a few relevant points from v7 to save a click or three. : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the : future. -[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com +[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com > > -See KVM_SET_USER_MEMORY_REGION. > > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and @@ -123,7 +123,7 @@ of private memory) all have the same ABI. Practically speaking, the cost to pKV (and likely every other CoCo VM type) is a single ioctl() during VM creation to "convert" all memory to private. -[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com +[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com > > --- /dev/null > > +++ b/virt/kvm/guest_memfd.c diff --git a/a/content_digest b/N1/content_digest index dc81c29..55f3ea3 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,15 +2,58 @@ "ref\020231027182217.3615211-17-seanjc@google.com\0" "ref\0CA+EHjTzj4drYKONVOLP19DYpJ4O8kSXcFzw2AKier1QdcFKx_Q@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@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 15:13:23 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Fuad Tabba <tabba@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> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + David Matlack <dmatlack@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 Tue, Oct 31, 2023, Fuad Tabba wrote:\n" "> Hi,\n" "> \n" - "> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Fri, Oct 27, 2023 at 7:23\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> \n" "> ...\n" "> \n" @@ -90,7 +133,7 @@ " : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the\n" " : future.\n" "\n" - "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com\n" + "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com\n" " \n" "> > -See KVM_SET_USER_MEMORY_REGION.\n" "> > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and\n" @@ -132,7 +175,7 @@ "(and likely every other CoCo VM type) is a single ioctl() during VM creation to\n" "\"convert\" all memory to private.\n" "\n" - "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com\n" + "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com\n" "\n" "> > --- /dev/null\n" "> > +++ b/virt/kvm/guest_memfd.c\n" @@ -204,4 +247,4 @@ "\n" Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? -c1b8847a6b8e437d9aedb3cb35b8f87b05394f86cad36b59e9d4b969d051bb19 +ec998abf58889c4d63ef71eb778d4c9fe474e068245199a14359eef53146fd06
diff --git a/a/1.txt b/N2/1.txt index 75be7e3..79377bc 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,7 +1,7 @@ On Tue, Oct 31, 2023, Fuad Tabba wrote: > Hi, > -> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote: +> On Fri, Oct 27, 2023 at 7:23 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > @@ -81,7 +81,7 @@ Copying a few relevant points from v7 to save a click or three. : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the : future. -[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com +[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com > > -See KVM_SET_USER_MEMORY_REGION. > > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and @@ -123,7 +123,7 @@ of private memory) all have the same ABI. Practically speaking, the cost to pKV (and likely every other CoCo VM type) is a single ioctl() during VM creation to "convert" all memory to private. -[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com +[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com > > --- /dev/null > > +++ b/virt/kvm/guest_memfd.c @@ -194,3 +194,8 @@ movement. I.e. the API is intended to be a "free arch metadata associated with the memslot". Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? + +_______________________________________________ +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 dc81c29..c768336 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,15 +2,58 @@ "ref\020231027182217.3615211-17-seanjc@google.com\0" "ref\0CA+EHjTzj4drYKONVOLP19DYpJ4O8kSXcFzw2AKier1QdcFKx_Q@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@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 15:13:23 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Fuad Tabba <tabba@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> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + David Matlack <dmatlack@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 Tue, Oct 31, 2023, Fuad Tabba wrote:\n" "> Hi,\n" "> \n" - "> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Fri, Oct 27, 2023 at 7:23\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> \n" "> ...\n" "> \n" @@ -90,7 +133,7 @@ " : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the\n" " : future.\n" "\n" - "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com\n" + "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com\n" " \n" "> > -See KVM_SET_USER_MEMORY_REGION.\n" "> > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and\n" @@ -132,7 +175,7 @@ "(and likely every other CoCo VM type) is a single ioctl() during VM creation to\n" "\"convert\" all memory to private.\n" "\n" - "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com\n" + "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com\n" "\n" "> > --- /dev/null\n" "> > +++ b/virt/kvm/guest_memfd.c\n" @@ -202,6 +245,11 @@ "movement. I.e. the API is intended to be a \"free arch metadata associated with\n" "the memslot\".\n" "\n" - Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? + "Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()?\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -c1b8847a6b8e437d9aedb3cb35b8f87b05394f86cad36b59e9d4b969d051bb19 +acb768d89524696805105281202b6fab33be06c44bdba234c4a08c5c93a8157c
diff --git a/a/1.txt b/N3/1.txt index 75be7e3..36d8211 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,7 +1,7 @@ On Tue, Oct 31, 2023, Fuad Tabba wrote: > Hi, > -> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote: +> On Fri, Oct 27, 2023 at 7:23 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > @@ -81,7 +81,7 @@ Copying a few relevant points from v7 to save a click or three. : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the : future. -[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com +[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com > > -See KVM_SET_USER_MEMORY_REGION. > > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and @@ -123,7 +123,7 @@ of private memory) all have the same ABI. Practically speaking, the cost to pKV (and likely every other CoCo VM type) is a single ioctl() during VM creation to "convert" all memory to private. -[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com +[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com > > --- /dev/null > > +++ b/virt/kvm/guest_memfd.c diff --git a/a/content_digest b/N3/content_digest index dc81c29..f4b8e6b 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,15 +2,42 @@ "ref\020231027182217.3615211-17-seanjc@google.com\0" "ref\0CA+EHjTzj4drYKONVOLP19DYpJ4O8kSXcFzw2AKier1QdcFKx_Q@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@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 15:13:23 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Fuad Tabba <tabba@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> + Vlastimil Babka <vbabka@suse.cz> + Yu Zhang <yu.c.zhang@linux.intel.com> + Maciej Szmigiero <mail@maciej.szmigiero.name> + Albert Ou <aou@eecs.berkeley.edu> + 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> + " Liam Merwick <liam.merwick@oracl>\0" "\00:1\0" "b\0" "On Tue, Oct 31, 2023, Fuad Tabba wrote:\n" "> Hi,\n" "> \n" - "> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Fri, Oct 27, 2023 at 7:23\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> \n" "> ...\n" "> \n" @@ -90,7 +117,7 @@ " : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the\n" " : future.\n" "\n" - "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com\n" + "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com\n" " \n" "> > -See KVM_SET_USER_MEMORY_REGION.\n" "> > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and\n" @@ -132,7 +159,7 @@ "(and likely every other CoCo VM type) is a single ioctl() during VM creation to\n" "\"convert\" all memory to private.\n" "\n" - "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com\n" + "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com\n" "\n" "> > --- /dev/null\n" "> > +++ b/virt/kvm/guest_memfd.c\n" @@ -204,4 +231,4 @@ "\n" Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? -c1b8847a6b8e437d9aedb3cb35b8f87b05394f86cad36b59e9d4b969d051bb19 +145473da20dd898b0c490f3eea22ea101d5d71b43e7d8d72f5a514371b903c65
diff --git a/a/1.txt b/N4/1.txt index 75be7e3..9cf1698 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -1,7 +1,7 @@ On Tue, Oct 31, 2023, Fuad Tabba wrote: > Hi, > -> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote: +> On Fri, Oct 27, 2023 at 7:23 PM Sean Christopherson <seanjc@google.com> wrote: > > ... > @@ -81,7 +81,7 @@ Copying a few relevant points from v7 to save a click or three. : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the : future. -[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com +[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com > > -See KVM_SET_USER_MEMORY_REGION. > > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and @@ -123,7 +123,7 @@ of private memory) all have the same ABI. Practically speaking, the cost to pKV (and likely every other CoCo VM type) is a single ioctl() during VM creation to "convert" all memory to private. -[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com +[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com > > --- /dev/null > > +++ b/virt/kvm/guest_memfd.c @@ -194,3 +194,8 @@ movement. I.e. the API is intended to be a "free arch metadata associated with the memslot". Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? + +_______________________________________________ +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 dc81c29..7a1992c 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -2,15 +2,58 @@ "ref\020231027182217.3615211-17-seanjc@google.com\0" "ref\0CA+EHjTzj4drYKONVOLP19DYpJ4O8kSXcFzw2AKier1QdcFKx_Q@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@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 15:13:23 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Fuad Tabba <tabba@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> + Jarkko Sakkinen <jarkko@kernel.org> + Anish Moorthy <amoorthy@google.com> + David Matlack <dmatlack@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 Tue, Oct 31, 2023, Fuad Tabba wrote:\n" "> Hi,\n" "> \n" - "> On Fri, Oct 27, 2023 at 7:23?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Fri, Oct 27, 2023 at 7:23\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> \n" "> ...\n" "> \n" @@ -90,7 +133,7 @@ " : just as good, go with PROTECTED as it gives us a wee bit of wiggle room for the\n" " : future.\n" "\n" - "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW at google.com\n" + "[*] https://lore.kernel.org/all/Yuh0ikhoh+tCK6VW@google.com\n" " \n" "> > -See KVM_SET_USER_MEMORY_REGION.\n" "> > +A KVM_MEM_PRIVATE region _must_ have a valid guest_memfd (private memory) and\n" @@ -132,7 +175,7 @@ "(and likely every other CoCo VM type) is a single ioctl() during VM creation to\n" "\"convert\" all memory to private.\n" "\n" - "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7 at google.com\n" + "[*] https://lore.kernel.org/all/ZRw6X2BptZnRPNK7@google.com\n" "\n" "> > --- /dev/null\n" "> > +++ b/virt/kvm/guest_memfd.c\n" @@ -202,6 +245,11 @@ "movement. I.e. the API is intended to be a \"free arch metadata associated with\n" "the memslot\".\n" "\n" - Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()? + "Out of curiosity, what does pKVM need to do at kvm_arch_guest_memory_reclaimed()?\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 -c1b8847a6b8e437d9aedb3cb35b8f87b05394f86cad36b59e9d4b969d051bb19 +d1732074a332fa218006e16fc5b2a6928c0e1be0e38f42dfb58259fe690e8b05
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.