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

diff --git a/a/1.txt b/N1/1.txt
index db30d92..22e20ad 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -53,3 +53,7 @@ memory is mutually exclusive, but simpler and more efficient overall.
 And separate address spaces become truly nasty if the CPU can access multiple
 protected regions, e.g. if the CPU can access type X and type Y at the same time,
 then there would need to be memslots for "regular", X, Y, and X+Y.
+_______________________________________________
+kvmarm mailing list
+kvmarm@lists.cs.columbia.edu
+https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
diff --git a/a/content_digest b/N1/content_digest
index 44d42ef..19877a8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,9 +4,42 @@
  "ref\0Y5NvYmxpy6BPkmpW@google.com\0"
  "ref\0CALzav=eju4LYyX=ufNneSww+5sraYJ8cfQSi4LTOHfHWmddX9A@mail.gmail.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
+ "Subject\0Re: [RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
  "Date\0Mon, 12 Dec 2022 17:39:38 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0David Matlack <dmatlack@google.com>\0"
+ "Cc\0Anshuman Khandual <anshuman.khandual@arm.com>"
+  Hugh Dickins <hughd@google.com>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Yang
+  Weijiang <weijiang.yang@intel.com>
+  Amit
+  Nadav <namit@vmware.com>
+  Colin Cross <ccross@google.com>
+  Ben Gardon <bgardon@google.com>
+  linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>
+  kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu>
+  Yu Zhao <yuzhao@google.com>
+  Marc Zyngier <maz@kernel.org>
+  Huacai Chen <chenhuacai@kernel.org>
+ " Matthew Wilcox \\(Oracle\\) <willy@infradead.org>"
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  Krish Sadhukhan <krish.sadhukhan@oracle.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Mingwei Zhang <mizhang@google.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  xu xin <cgel.zte@gmail.com>
+  Arnd Bergmann <arnd@arndb.de>
+  Liam R. Howlett <Liam.Howlett@oracle.com>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  Atish Patra <atishp@atishpatra.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  Suren Baghdasaryan <surenb@google.com>
+  Vlastimil Babka <vbabka@suse.cz>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+  Paolo Bonzini <pbonzini@redhat.com>
+ " Andrew Morton <akpm@linux-foundation.org>\0"
  "\00:1\0"
  "b\0"
  "On Fri, Dec 09, 2022, David Matlack wrote:\n"
@@ -63,6 +96,10 @@
  "\n"
  "And separate address spaces become truly nasty if the CPU can access multiple\n"
  "protected regions, e.g. if the CPU can access type X and type Y at the same time,\n"
- "then there would need to be memslots for \"regular\", X, Y, and X+Y."
+ "then there would need to be memslots for \"regular\", X, Y, and X+Y.\n"
+ "_______________________________________________\n"
+ "kvmarm mailing list\n"
+ "kvmarm@lists.cs.columbia.edu\n"
+ https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
 
-1e41fbb4bed128a693b4a89be62122f12f31e9519efbd2a5f6aec3157759e7c1
+db9fbb2a6364dd6ba48397ef8051353a103e52a813bdd70d6cb43b94bcc310a3

diff --git a/a/content_digest b/N2/content_digest
index 44d42ef..49f5c13 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -4,9 +4,50 @@
  "ref\0Y5NvYmxpy6BPkmpW@google.com\0"
  "ref\0CALzav=eju4LYyX=ufNneSww+5sraYJ8cfQSi4LTOHfHWmddX9A@mail.gmail.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
+ "Subject\0Re: [RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
  "Date\0Mon, 12 Dec 2022 17:39:38 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0David Matlack <dmatlack@google.com>\0"
+ "Cc\0Oliver Upton <oliver.upton@linux.dev>"
+  Yang
+  Weijiang <weijiang.yang@intel.com>
+  Paolo Bonzini <pbonzini@redhat.com>
+  Marc Zyngier <maz@kernel.org>
+  James Morse <james.morse@arm.com>
+  Alexandru Elisei <alexandru.elisei@arm.com>
+  Suzuki K Poulose <suzuki.poulose@arm.com>
+  Huacai Chen <chenhuacai@kernel.org>
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  Anup Patel <anup@brainfault.org>
+  Atish Patra <atishp@atishpatra.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Andrew Morton <akpm@linux-foundation.org>
+  Anshuman Khandual <anshuman.khandual@arm.com>
+  Amit
+  Nadav <namit@vmware.com>
+  Matthew Wilcox (Oracle) <willy@infradead.org>
+  Vlastimil Babka <vbabka@suse.cz>
+  Liam R. Howlett <Liam.Howlett@oracle.com>
+  Suren Baghdasaryan <surenb@google.com>
+  Peter Xu <peterx@redhat.com>
+  xu xin <cgel.zte@gmail.com>
+  Arnd Bergmann <arnd@arndb.de>
+  Yu Zhao <yuzhao@google.com>
+  Colin Cross <ccross@google.com>
+  Hugh Dickins <hughd@google.com>
+  Ben Gardon <bgardon@google.com>
+  Mingwei Zhang <mizhang@google.com>
+  Krish Sadhukhan <krish.sadhukhan@oracle.com>
+  Ricardo Koller <ricarkol@google.com>
+  Jing Zhang <jingzhangos@google.com>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+ " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "On Fri, Dec 09, 2022, David Matlack wrote:\n"
@@ -65,4 +106,4 @@
  "protected regions, e.g. if the CPU can access type X and type Y at the same time,\n"
  "then there would need to be memslots for \"regular\", X, Y, and X+Y."
 
-1e41fbb4bed128a693b4a89be62122f12f31e9519efbd2a5f6aec3157759e7c1
+20aa209e6406ee242c84fa9c0c28946107e70e0ae3b8c9584a3de472bc5a26f6

diff --git a/a/1.txt b/N3/1.txt
index db30d92..66fb341 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -53,3 +53,8 @@ memory is mutually exclusive, but simpler and more efficient overall.
 And separate address spaces become truly nasty if the CPU can access multiple
 protected regions, e.g. if the CPU can access type X and type Y at the same time,
 then there would need to be memslots for "regular", X, Y, and X+Y.
+
+_______________________________________________
+linux-riscv mailing list
+linux-riscv@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/a/content_digest b/N3/content_digest
index 44d42ef..a18727f 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -4,9 +4,50 @@
  "ref\0Y5NvYmxpy6BPkmpW@google.com\0"
  "ref\0CALzav=eju4LYyX=ufNneSww+5sraYJ8cfQSi4LTOHfHWmddX9A@mail.gmail.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
+ "Subject\0Re: [RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
  "Date\0Mon, 12 Dec 2022 17:39:38 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0David Matlack <dmatlack@google.com>\0"
+ "Cc\0Oliver Upton <oliver.upton@linux.dev>"
+  Yang
+  Weijiang <weijiang.yang@intel.com>
+  Paolo Bonzini <pbonzini@redhat.com>
+  Marc Zyngier <maz@kernel.org>
+  James Morse <james.morse@arm.com>
+  Alexandru Elisei <alexandru.elisei@arm.com>
+  Suzuki K Poulose <suzuki.poulose@arm.com>
+  Huacai Chen <chenhuacai@kernel.org>
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  Anup Patel <anup@brainfault.org>
+  Atish Patra <atishp@atishpatra.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Andrew Morton <akpm@linux-foundation.org>
+  Anshuman Khandual <anshuman.khandual@arm.com>
+  Amit
+  Nadav <namit@vmware.com>
+  Matthew Wilcox (Oracle) <willy@infradead.org>
+  Vlastimil Babka <vbabka@suse.cz>
+  Liam R. Howlett <Liam.Howlett@oracle.com>
+  Suren Baghdasaryan <surenb@google.com>
+  Peter Xu <peterx@redhat.com>
+  xu xin <cgel.zte@gmail.com>
+  Arnd Bergmann <arnd@arndb.de>
+  Yu Zhao <yuzhao@google.com>
+  Colin Cross <ccross@google.com>
+  Hugh Dickins <hughd@google.com>
+  Ben Gardon <bgardon@google.com>
+  Mingwei Zhang <mizhang@google.com>
+  Krish Sadhukhan <krish.sadhukhan@oracle.com>
+  Ricardo Koller <ricarkol@google.com>
+  Jing Zhang <jingzhangos@google.com>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+ " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "On Fri, Dec 09, 2022, David Matlack wrote:\n"
@@ -63,6 +104,11 @@
  "\n"
  "And separate address spaces become truly nasty if the CPU can access multiple\n"
  "protected regions, e.g. if the CPU can access type X and type Y at the same time,\n"
- "then there would need to be memslots for \"regular\", X, Y, and X+Y."
+ "then there would need to be memslots for \"regular\", X, Y, and X+Y.\n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-1e41fbb4bed128a693b4a89be62122f12f31e9519efbd2a5f6aec3157759e7c1
+9ba60360e49d1fb97e4550c2cc398ce664cfdf38b878bd5aad4c38dbd458c402

diff --git a/a/1.txt b/N4/1.txt
index db30d92..bb3ad48 100644
--- a/a/1.txt
+++ b/N4/1.txt
@@ -53,3 +53,8 @@ memory is mutually exclusive, but simpler and more efficient overall.
 And separate address spaces become truly nasty if the CPU can access multiple
 protected regions, e.g. if the CPU can access type X and type Y at the same time,
 then there would need to be memslots for "regular", X, Y, and X+Y.
+
+_______________________________________________
+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 44d42ef..a8eadbe 100644
--- a/a/content_digest
+++ b/N4/content_digest
@@ -4,9 +4,50 @@
  "ref\0Y5NvYmxpy6BPkmpW@google.com\0"
  "ref\0CALzav=eju4LYyX=ufNneSww+5sraYJ8cfQSi4LTOHfHWmddX9A@mail.gmail.com\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
+ "Subject\0Re: [RFC PATCH 01/37] KVM: x86/mmu: Store the address space ID directly in kvm_mmu_page_role\0"
  "Date\0Mon, 12 Dec 2022 17:39:38 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0David Matlack <dmatlack@google.com>\0"
+ "Cc\0Oliver Upton <oliver.upton@linux.dev>"
+  Yang
+  Weijiang <weijiang.yang@intel.com>
+  Paolo Bonzini <pbonzini@redhat.com>
+  Marc Zyngier <maz@kernel.org>
+  James Morse <james.morse@arm.com>
+  Alexandru Elisei <alexandru.elisei@arm.com>
+  Suzuki K Poulose <suzuki.poulose@arm.com>
+  Huacai Chen <chenhuacai@kernel.org>
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  Anup Patel <anup@brainfault.org>
+  Atish Patra <atishp@atishpatra.org>
+  Paul Walmsley <paul.walmsley@sifive.com>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Albert Ou <aou@eecs.berkeley.edu>
+  Andrew Morton <akpm@linux-foundation.org>
+  Anshuman Khandual <anshuman.khandual@arm.com>
+  Amit
+  Nadav <namit@vmware.com>
+  Matthew Wilcox (Oracle) <willy@infradead.org>
+  Vlastimil Babka <vbabka@suse.cz>
+  Liam R. Howlett <Liam.Howlett@oracle.com>
+  Suren Baghdasaryan <surenb@google.com>
+  Peter Xu <peterx@redhat.com>
+  xu xin <cgel.zte@gmail.com>
+  Arnd Bergmann <arnd@arndb.de>
+  Yu Zhao <yuzhao@google.com>
+  Colin Cross <ccross@google.com>
+  Hugh Dickins <hughd@google.com>
+  Ben Gardon <bgardon@google.com>
+  Mingwei Zhang <mizhang@google.com>
+  Krish Sadhukhan <krish.sadhukhan@oracle.com>
+  Ricardo Koller <ricarkol@google.com>
+  Jing Zhang <jingzhangos@google.com>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  kvmarm@lists.linux.dev <kvmarm@lists.linux.dev>
+  kvmarm@lists.cs.columbia.edu <kvmarm@lists.cs.columbia.edu>
+  linux-mips@vger.kernel.org <linux-mips@vger.kernel.org>
+  kvm@vger.kernel.org <kvm@vger.kernel.org>
+  kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org>
+ " linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "On Fri, Dec 09, 2022, David Matlack wrote:\n"
@@ -63,6 +104,11 @@
  "\n"
  "And separate address spaces become truly nasty if the CPU can access multiple\n"
  "protected regions, e.g. if the CPU can access type X and type Y at the same time,\n"
- "then there would need to be memslots for \"regular\", X, Y, and X+Y."
+ "then there would need to be memslots for \"regular\", X, Y, and X+Y.\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
 
-1e41fbb4bed128a693b4a89be62122f12f31e9519efbd2a5f6aec3157759e7c1
+d4b581d51a4da9971cc79a162c9d9ffc0e11b5eda6d87d1c0555a51356626294

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.