All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <ZU51A3U6E3aZXayC@google.com>

diff --git a/a/content_digest b/N1/content_digest
index 7a2b318..875c37e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,9 +2,52 @@
  "ref\020231105163040.14904-16-pbonzini@redhat.com\0"
  "ref\0956d8ee3-8b63-4a2d-b0c4-c0d3d74a0f6f@intel.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
+ "Subject\0Re: [PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
  "Date\0Fri, 10 Nov 2023 10:22:59 -0800\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Xiaoyao Li <xiaoyao.li@intel.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
+  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>
+  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 Fri, Nov 10, 2023, Xiaoyao Li wrote:\n"
@@ -99,4 +142,4 @@
  "There's no harm to KVM if userspace creates a file it can't use, and at some\n"
  point KVM will hopefully support guest_memfd irrespective of private memory.
 
-1efc896fe821a24d849b1fc4e7e22ce97f2abd4d9a50cfe521da4865ac75021b
+8e4e91ea50316db8ce2d3776147ff99a67bdf09b795e30b8f8a668d4eb248509

diff --git a/a/1.txt b/N2/1.txt
index 06c13f5..4ab7e13 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -89,3 +89,8 @@ So my vote is to do:
 
 There's no harm to KVM if userspace creates a file it can't use, and at some
 point KVM will hopefully support guest_memfd irrespective of private memory.
+
+_______________________________________________
+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 7a2b318..ca7608f 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,9 +2,52 @@
  "ref\020231105163040.14904-16-pbonzini@redhat.com\0"
  "ref\0956d8ee3-8b63-4a2d-b0c4-c0d3d74a0f6f@intel.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
+ "Subject\0Re: [PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
  "Date\0Fri, 10 Nov 2023 10:22:59 -0800\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Xiaoyao Li <xiaoyao.li@intel.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
+  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>
+  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 Fri, Nov 10, 2023, Xiaoyao Li wrote:\n"
@@ -97,6 +140,11 @@
  "\t\treturn IS_ENABLED(CONFIG_KVM_PRIVATE_MEM);\n"
  "\n"
  "There's no harm to KVM if userspace creates a file it can't use, and at some\n"
- point KVM will hopefully support guest_memfd irrespective of private memory.
+ "point KVM will hopefully support guest_memfd irrespective of private memory.\n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-1efc896fe821a24d849b1fc4e7e22ce97f2abd4d9a50cfe521da4865ac75021b
+7af91ef8f05cbda286bb18883ee21fdbc4d4450a5389e886a2cef68f6a9d1ba9

diff --git a/a/content_digest b/N3/content_digest
index 7a2b318..81ae2b8 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -2,9 +2,36 @@
  "ref\020231105163040.14904-16-pbonzini@redhat.com\0"
  "ref\0956d8ee3-8b63-4a2d-b0c4-c0d3d74a0f6f@intel.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
+ "Subject\0Re: [PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
  "Date\0Fri, 10 Nov 2023 10:22:59 -0800\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Xiaoyao Li <xiaoyao.li@intel.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>
+  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>
+ " Liam Merwick <liam.merwick@oracle.co>\0"
  "\00:1\0"
  "b\0"
  "On Fri, Nov 10, 2023, Xiaoyao Li wrote:\n"
@@ -99,4 +126,4 @@
  "There's no harm to KVM if userspace creates a file it can't use, and at some\n"
  point KVM will hopefully support guest_memfd irrespective of private memory.
 
-1efc896fe821a24d849b1fc4e7e22ce97f2abd4d9a50cfe521da4865ac75021b
+a67705680b615e4289e797a7a12d961d304aba9a0d5361b747111ec364e5030a

diff --git a/a/1.txt b/N4/1.txt
index 06c13f5..f172344 100644
--- a/a/1.txt
+++ b/N4/1.txt
@@ -89,3 +89,8 @@ So my vote is to do:
 
 There's no harm to KVM if userspace creates a file it can't use, and at some
 point KVM will hopefully support guest_memfd irrespective of private memory.
+
+_______________________________________________
+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 7a2b318..7dc55f9 100644
--- a/a/content_digest
+++ b/N4/content_digest
@@ -2,9 +2,52 @@
  "ref\020231105163040.14904-16-pbonzini@redhat.com\0"
  "ref\0956d8ee3-8b63-4a2d-b0c4-c0d3d74a0f6f@intel.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
+ "Subject\0Re: [PATCH 15/34] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0"
  "Date\0Fri, 10 Nov 2023 10:22:59 -0800\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0Xiaoyao Li <xiaoyao.li@intel.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
+  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>
+  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 Fri, Nov 10, 2023, Xiaoyao Li wrote:\n"
@@ -97,6 +140,11 @@
  "\t\treturn IS_ENABLED(CONFIG_KVM_PRIVATE_MEM);\n"
  "\n"
  "There's no harm to KVM if userspace creates a file it can't use, and at some\n"
- point KVM will hopefully support guest_memfd irrespective of private memory.
+ "point KVM will hopefully support guest_memfd irrespective of private memory.\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
 
-1efc896fe821a24d849b1fc4e7e22ce97f2abd4d9a50cfe521da4865ac75021b
+2a1d4d7a26662ab2f85ef6e9413c7eb5d0b948ffcb50027610cceae40d7d0305

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.