diff for duplicates of <ZUKMsOdg3N9wmEzy@google.com> diff --git a/a/1.txt b/N1/1.txt index 808eef2..94d55fe 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -39,7 +39,7 @@ subtly tricky because KVM's (again, poorly documented) ABI is that *some* exit reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a pending signal). -https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com +https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com > [...] > @@ -69,4 +69,4 @@ I'd prefer to keep it in generic code, as it's highly likely to end up there sooner than later. There's a known use case for ARM (exit to userspace on missing userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API. -[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com +[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com diff --git a/a/content_digest b/N1/content_digest index 94997df..ec30d96 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,9 +2,53 @@ "ref\020231027182217.3615211-10-seanjc@google.com\0" "ref\0482bfea6f54ea1bb7d1ad75e03541d0ba0e5be6f.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Wed, 1 Nov 2023 10:36:48 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Kai Huang <kai.huang@intel.com>\0" + "Cc\0viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + brauner@kernel.org <brauner@kernel.org> + oliver.upton@linux.dev <oliver.upton@linux.dev> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + pbonzini@redhat.com <pbonzini@redhat.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + willy@infradead.org <willy@infradead.org> + anup@brainfault.org <anup@brainfault.org> + akpm@linux-foundation.org <akpm@linux-foundation.org> + Xiaoyao Li <xiaoyao.li@intel.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + mic@digikod.net <mic@digikod.net> + liam.merwick@oracle.com <liam.merwick@oracle.com> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Isaku Yamahata <isaku.yamahata@intel.com> + kirill.shutemov@linux.intel.com <kirill.shutemov@linux.intel.com> + david@redhat.com <david@redhat.com> + tabba@google.com <tabba@google.com> + amoorthy@google.com <amoorthy@google.com> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + michael.roth@amd.com <michael.roth@amd.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> + linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> + chao.p.peng@linux.intel.com <chao.p.peng@linux.intel.com> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + Vishal Annapurve <vannapurve@google.com> + vbabka@suse.cz <vbabka@suse.cz> + mail@maciej.szmigiero.name <mail@maciej.szmigiero.name> + yu.c.zhang@linux.intel.com <yu.c.zhang@linux.intel.com> + qperret@google.com <qperret@google.com> + dmatlack@google.com <dmatlack@google.com> + Yilun Xu <yilun.xu@intel.com> + isaku.yamahata@gmail.com <isaku.yamahata@gmail.com> + ackerleytng@google.com <ackerleytng@google.com> + jarkko@kernel.org <jarkko@kernel.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mm@kvack.org <linux-mm@kvack.org> + " Wei W Wang <wei.w.wang@intel.com>\0" "\00:1\0" "b\0" "On Wed, Nov 01, 2023, Kai Huang wrote:\n" @@ -48,7 +92,7 @@ "reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a\n" "pending signal).\n" "\n" - "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com\n" + "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com\n" "\n" "> [...]\n" "> \n" @@ -78,6 +122,6 @@ "sooner than later. There's a known use case for ARM (exit to userspace on missing\n" "userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API.\n" "\n" - [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com + [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com -ca8386f265b6b63eb90d275228c0ae46929f5bd753b269f846d7a80bbcfd1c84 +e401c6196cfe28266caffeee8e9d9615355dd26ec711ac390b4d3f8cff92dc5b
diff --git a/a/1.txt b/N2/1.txt index 808eef2..9fd0a36 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -39,7 +39,7 @@ subtly tricky because KVM's (again, poorly documented) ABI is that *some* exit reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a pending signal). -https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com +https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com > [...] > @@ -69,4 +69,9 @@ I'd prefer to keep it in generic code, as it's highly likely to end up there sooner than later. There's a known use case for ARM (exit to userspace on missing userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API. -[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com +[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com + +_______________________________________________ +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 94997df..1d35e0d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,9 +2,53 @@ "ref\020231027182217.3615211-10-seanjc@google.com\0" "ref\0482bfea6f54ea1bb7d1ad75e03541d0ba0e5be6f.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Wed, 1 Nov 2023 10:36:48 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Kai Huang <kai.huang@intel.com>\0" + "Cc\0viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + brauner@kernel.org <brauner@kernel.org> + oliver.upton@linux.dev <oliver.upton@linux.dev> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + pbonzini@redhat.com <pbonzini@redhat.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + willy@infradead.org <willy@infradead.org> + anup@brainfault.org <anup@brainfault.org> + akpm@linux-foundation.org <akpm@linux-foundation.org> + Xiaoyao Li <xiaoyao.li@intel.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + mic@digikod.net <mic@digikod.net> + liam.merwick@oracle.com <liam.merwick@oracle.com> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Isaku Yamahata <isaku.yamahata@intel.com> + kirill.shutemov@linux.intel.com <kirill.shutemov@linux.intel.com> + david@redhat.com <david@redhat.com> + tabba@google.com <tabba@google.com> + amoorthy@google.com <amoorthy@google.com> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + michael.roth@amd.com <michael.roth@amd.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> + linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> + chao.p.peng@linux.intel.com <chao.p.peng@linux.intel.com> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + Vishal Annapurve <vannapurve@google.com> + vbabka@suse.cz <vbabka@suse.cz> + mail@maciej.szmigiero.name <mail@maciej.szmigiero.name> + yu.c.zhang@linux.intel.com <yu.c.zhang@linux.intel.com> + qperret@google.com <qperret@google.com> + dmatlack@google.com <dmatlack@google.com> + Yilun Xu <yilun.xu@intel.com> + isaku.yamahata@gmail.com <isaku.yamahata@gmail.com> + ackerleytng@google.com <ackerleytng@google.com> + jarkko@kernel.org <jarkko@kernel.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mm@kvack.org <linux-mm@kvack.org> + " Wei W Wang <wei.w.wang@intel.com>\0" "\00:1\0" "b\0" "On Wed, Nov 01, 2023, Kai Huang wrote:\n" @@ -48,7 +92,7 @@ "reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a\n" "pending signal).\n" "\n" - "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com\n" + "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com\n" "\n" "> [...]\n" "> \n" @@ -78,6 +122,11 @@ "sooner than later. There's a known use case for ARM (exit to userspace on missing\n" "userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API.\n" "\n" - [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com + "[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -ca8386f265b6b63eb90d275228c0ae46929f5bd753b269f846d7a80bbcfd1c84 +5fff5aead7958ee73461abb1139130f7bdec71d2d574a5d6ad8c21c1c71a7b32
diff --git a/a/1.txt b/N3/1.txt index 808eef2..94d55fe 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -39,7 +39,7 @@ subtly tricky because KVM's (again, poorly documented) ABI is that *some* exit reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a pending signal). -https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com +https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com > [...] > @@ -69,4 +69,4 @@ I'd prefer to keep it in generic code, as it's highly likely to end up there sooner than later. There's a known use case for ARM (exit to userspace on missing userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API. -[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com +[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com diff --git a/a/content_digest b/N3/content_digest index 94997df..3cc5526 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,9 +2,52 @@ "ref\020231027182217.3615211-10-seanjc@google.com\0" "ref\0482bfea6f54ea1bb7d1ad75e03541d0ba0e5be6f.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Wed, 1 Nov 2023 10:36:48 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Kai Huang <kai.huang@intel.com>\0" + "Cc\0kvm@vger.kernel.org <kvm@vger.kernel.org>" + david@redhat.com <david@redhat.com> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + linux-mm@kvack.org <linux-mm@kvack.org> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + pbonzini@redhat.com <pbonzini@redhat.com> + chao.p.peng@linux.intel.com <chao.p.peng@linux.intel.com> + linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> + isaku.yamahata@gmail.com <isaku.yamahata@gmail.com> + chenhuacai@kernel.org <chenhuacai@kernel.org> + Xiaoyao Li <xiaoyao.li@intel.com> + willy@infradead.org <willy@infradead.org> + Wei W Wang <wei.w.wang@intel.com> + vbabka@suse.cz <vbabka@suse.cz> + yu.c.zhang@linux.intel.com <yu.c.zhang@linux.intel.com> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + mail@maciej.szmigiero.name <mail@maciej.szmigiero.name> + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + michael.roth@amd.com <michael.roth@amd.com> + ackerleytng@google.com <ackerleyt ng@google.com> + viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + mic@digikod.net <mic@digikod.net> + tabba@google.com <tabba@google.com> + Isaku Yamahata <isaku.yamahata@intel.com> + brauner@kernel.org <brauner@kernel.org> + qperret@google.com <qperret@google.com> + anup@brainfault.org <anup@brainfault.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + oliver.upton@linux.dev <oliver.upton@linux.dev> + dmatlack@google.com <dmatlack@google.com> + jarkko@kernel.org <jarkko@kernel.org> + palmer@dabbelt.com <palmer@dabbelt.com> + amoorthy@google.com <amoorthy@google.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + maz@kernel.org <maz@kernel.org> + linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> + liam.merwick@oracle.com <liam.merwick@oracle.com> + akpm@linux-foundation.org <akpm@linux-foundation.org> + Vishal Annapurve <vannapurve@google.com> + linuxppc-dev@list s.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + Yilun Xu <yilun.xu@intel.com> + " kirill.shutemov@linux.intel.com <kirill.shutemov@linux.intel.com>\0" "\00:1\0" "b\0" "On Wed, Nov 01, 2023, Kai Huang wrote:\n" @@ -48,7 +91,7 @@ "reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a\n" "pending signal).\n" "\n" - "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com\n" + "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com\n" "\n" "> [...]\n" "> \n" @@ -78,6 +121,6 @@ "sooner than later. There's a known use case for ARM (exit to userspace on missing\n" "userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API.\n" "\n" - [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com + [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com -ca8386f265b6b63eb90d275228c0ae46929f5bd753b269f846d7a80bbcfd1c84 +021545a0f0fabc21f1c9b45d75ad3979956ada16a1f812c687274e70848154bd
diff --git a/a/1.txt b/N4/1.txt index 808eef2..cb31087 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -39,7 +39,7 @@ subtly tricky because KVM's (again, poorly documented) ABI is that *some* exit reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a pending signal). -https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com +https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com > [...] > @@ -69,4 +69,9 @@ I'd prefer to keep it in generic code, as it's highly likely to end up there sooner than later. There's a known use case for ARM (exit to userspace on missing userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API. -[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com +[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com + +_______________________________________________ +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 94997df..fb1dbe2 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -2,9 +2,53 @@ "ref\020231027182217.3615211-10-seanjc@google.com\0" "ref\0482bfea6f54ea1bb7d1ad75e03541d0ba0e5be6f.camel@intel.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" + "Subject\0Re: [PATCH v13 09/35] KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace\0" "Date\0Wed, 1 Nov 2023 10:36:48 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Kai Huang <kai.huang@intel.com>\0" + "Cc\0viro@zeniv.linux.org.uk <viro@zeniv.linux.org.uk>" + aou@eecs.berkeley.edu <aou@eecs.berkeley.edu> + brauner@kernel.org <brauner@kernel.org> + oliver.upton@linux.dev <oliver.upton@linux.dev> + chenhuacai@kernel.org <chenhuacai@kernel.org> + paul.walmsley@sifive.com <paul.walmsley@sifive.com> + palmer@dabbelt.com <palmer@dabbelt.com> + maz@kernel.org <maz@kernel.org> + pbonzini@redhat.com <pbonzini@redhat.com> + mpe@ellerman.id.au <mpe@ellerman.id.au> + willy@infradead.org <willy@infradead.org> + anup@brainfault.org <anup@brainfault.org> + akpm@linux-foundation.org <akpm@linux-foundation.org> + Xiaoyao Li <xiaoyao.li@intel.com> + kvm-riscv@lists.infradead.org <kvm-riscv@lists.infradead.org> + mic@digikod.net <mic@digikod.net> + liam.merwick@oracle.com <liam.merwick@oracle.com> + kvm@vger.kernel.org <kvm@vger.kernel.org> + Isaku Yamahata <isaku.yamahata@intel.com> + kirill.shutemov@linux.intel.com <kirill.shutemov@linux.intel.com> + david@redhat.com <david@redhat.com> + tabba@google.com <tabba@google.com> + amoorthy@google.com <amoorthy@google.com> + linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> + michael.roth@amd.com <michael.roth@amd.com> + kvmarm@lists.linux.dev <kvmarm@lists.linux.dev> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + linux-fsdevel@vger.kernel.org <linux-fsdevel@vger.kernel.org> + linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> + chao.p.peng@linux.intel.com <chao.p.peng@linux.intel.com> + linux-mips@vger.kernel.org <linux-mips@vger.kernel.org> + Vishal Annapurve <vannapurve@google.com> + vbabka@suse.cz <vbabka@suse.cz> + mail@maciej.szmigiero.name <mail@maciej.szmigiero.name> + yu.c.zhang@linux.intel.com <yu.c.zhang@linux.intel.com> + qperret@google.com <qperret@google.com> + dmatlack@google.com <dmatlack@google.com> + Yilun Xu <yilun.xu@intel.com> + isaku.yamahata@gmail.com <isaku.yamahata@gmail.com> + ackerleytng@google.com <ackerleytng@google.com> + jarkko@kernel.org <jarkko@kernel.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-mm@kvack.org <linux-mm@kvack.org> + " Wei W Wang <wei.w.wang@intel.com>\0" "\00:1\0" "b\0" "On Wed, Nov 01, 2023, Kai Huang wrote:\n" @@ -48,7 +92,7 @@ "reasons are preserved across KVM_RUN with vcpu->run->immediate_exit (or with a\n" "pending signal).\n" "\n" - "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf at google.com\n" + "https://lore.kernel.org/all/ZFFbwOXZ5uI%2Fgdaf@google.com\n" "\n" "> [...]\n" "> \n" @@ -78,6 +122,11 @@ "sooner than later. There's a known use case for ARM (exit to userspace on missing\n" "userspace mapping[*]), and I'm guessing pKVM (also ARM) will also utilize this API.\n" "\n" - [*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy at google.com + "[*] https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\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 -ca8386f265b6b63eb90d275228c0ae46929f5bd753b269f846d7a80bbcfd1c84 +43e3754da23216a16ddd74f1a33be1df027c8ccf9e616d32fd526094c89549de
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.