diff for duplicates of <ZSmQUyfldIMMpx7X@google.com> diff --git a/a/1.txt b/N1/1.txt index 463f2b5..a2bc4b7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,8 +1,8 @@ On Tue, Oct 10, 2023, David Matlack wrote: -> On Thu, Oct 5, 2023 at 3:46?PM Sean Christopherson <seanjc@google.com> wrote: +> On Thu, Oct 5, 2023 at 3:46 PM Sean Christopherson <seanjc@google.com> wrote: > > > > On Thu, Oct 05, 2023, Anish Moorthy wrote: -> > > On Tue, Oct 3, 2023 at 4:46?PM Sean Christopherson <seanjc@google.com> wrote: +> > > On Tue, Oct 3, 2023 at 4:46 PM Sean Christopherson <seanjc@google.com> wrote: > > > > > > > > The only way a KVM_EXIT_MEMORY_FAULT that actually reaches userspace could be > > > > "unreliable" is if something other than a memory_fault exit clobbered the union, @@ -103,4 +103,4 @@ page fault, then odds are very good that the bug would result in KVM returning a "bare" -EFAULT regardless of whether KVM_EXIT_MEMORY_FAULT is paried with '0' or -EFAULT. -[*] https://lore.kernel.org/all/ZQHzVOIsesTTysgf at google.com +[*] https://lore.kernel.org/all/ZQHzVOIsesTTysgf@google.com diff --git a/a/content_digest b/N1/content_digest index b677146..8c37751 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,16 +9,44 @@ "ref\0ZR88w9W62qsZDro-@google.com\0" "ref\0CALzav=csPcd3f5CYc=6Fa4JnsYP8UTVeSex0-7LvUBnTDpHxLQ@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v12 07/33] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [RFC PATCH v12 07/33] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Fri, 13 Oct 2023 11:45:39 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0David Matlack <dmatlack@google.com>\0" + "Cc\0Anish Moorthy <amoorthy@google.com>" + Xiaoyao Li <xiaoyao.li@intel.com> + Paolo 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> + kvm@vger.kernel.org + kvmarm@lists.linux.dev + kvm-riscv@lists.infradead.org + linux-kernel@vger.kernel.org + Chao Peng <chao.p.peng@linux.intel.com> + Fuad Tabba <tabba@google.com> + Jarkko Sakkinen <jarkko@kernel.org> + Yu Zhang <yu.c.zhang@linux.intel.com> + Isaku Yamahata <isaku.yamahata@intel.com> + Xu Yilun <yilun.xu@intel.com> + 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>\0" "\00:1\0" "b\0" "On Tue, Oct 10, 2023, David Matlack wrote:\n" - "> On Thu, Oct 5, 2023 at 3:46?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Thu, Oct 5, 2023 at 3:46\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> >\n" "> > On Thu, Oct 05, 2023, Anish Moorthy wrote:\n" - "> > > On Tue, Oct 3, 2023 at 4:46?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> > > On Tue, Oct 3, 2023 at 4:46\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > > >\n" "> > > > The only way a KVM_EXIT_MEMORY_FAULT that actually reaches userspace could be\n" "> > > > \"unreliable\" is if something other than a memory_fault exit clobbered the union,\n" @@ -119,6 +147,6 @@ "\"bare\" -EFAULT regardless of whether KVM_EXIT_MEMORY_FAULT is paried with '0' or\n" "-EFAULT.\n" "\n" - [*] https://lore.kernel.org/all/ZQHzVOIsesTTysgf at google.com + [*] https://lore.kernel.org/all/ZQHzVOIsesTTysgf@google.com -822c5d10c9535f2bc977330647b55f0addf17577527c818dddb7456da2426dfc +a532b84fee269ed2f47b3d56ed0eb8ffca1eb222fda3e888bb883bb197d032b7
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.