diff for duplicates of <ZUPFmwWjPFlXRlPi@google.com> diff --git a/a/1.txt b/N1/1.txt index ec80bef..938c63a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,7 +6,7 @@ On Thu, Nov 02, 2023, Xiaoyao Li wrote: > > 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 > > I wonder how this CAP is supposed to be checked in userspace, for guest > memfd case? diff --git a/a/content_digest b/N1/content_digest index 3031b8a..6e1275f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,9 +4,53 @@ "ref\0ZUKMsOdg3N9wmEzy@google.com\0" "ref\033686031-c1df-4ef5-a6ac-1aab7f5c656e@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\0Thu, 2 Nov 2023 08:51:55 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Kai Huang <kai.huang@intel.com>" + viro@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> + 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 Thu, Nov 02, 2023, Xiaoyao Li wrote:\n" @@ -17,7 +61,7 @@ "> > 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\n" + "> > [*]https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\n" "> \n" "> I wonder how this CAP is supposed to be checked in userspace, for guest\n" "> memfd case? \n" @@ -50,4 +94,4 @@ "\tif (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO))\n" "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");" -0788b0c17d5f0513043e95cb632ffff9c58f3e0bfab0bc987ee2d9135eb5de4f +a5ea988774253e870495e9515f641b56650c08ade55c1d7b9b6faf166c9309f3
diff --git a/a/1.txt b/N2/1.txt index ec80bef..148c722 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,7 +6,7 @@ On Thu, Nov 02, 2023, Xiaoyao Li wrote: > > 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 > > I wonder how this CAP is supposed to be checked in userspace, for guest > memfd case? @@ -38,3 +38,10 @@ supported, i.e. userspace should be able to do: if (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO)) abort("KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ"); + + + +_______________________________________________ +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 3031b8a..8c5c8f1 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -4,9 +4,53 @@ "ref\0ZUKMsOdg3N9wmEzy@google.com\0" "ref\033686031-c1df-4ef5-a6ac-1aab7f5c656e@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\0Thu, 2 Nov 2023 08:51:55 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Kai Huang <kai.huang@intel.com>" + viro@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> + 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 Thu, Nov 02, 2023, Xiaoyao Li wrote:\n" @@ -17,7 +61,7 @@ "> > 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\n" + "> > [*]https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\n" "> \n" "> I wonder how this CAP is supposed to be checked in userspace, for guest\n" "> memfd case? \n" @@ -48,6 +92,13 @@ "supported, i.e. userspace should be able to do:\n" "\n" "\tif (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO))\n" - "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");" + "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");\n" + "\n" + "\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -0788b0c17d5f0513043e95cb632ffff9c58f3e0bfab0bc987ee2d9135eb5de4f +57b214aca4edca87be550a31156044298d789bc654d8f49be47905a7dddce8ea
diff --git a/a/1.txt b/N3/1.txt index ec80bef..938c63a 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -6,7 +6,7 @@ On Thu, Nov 02, 2023, Xiaoyao Li wrote: > > 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 > > I wonder how this CAP is supposed to be checked in userspace, for guest > memfd case? diff --git a/a/content_digest b/N3/content_digest index 3031b8a..21de2d6 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -4,9 +4,52 @@ "ref\0ZUKMsOdg3N9wmEzy@google.com\0" "ref\033686031-c1df-4ef5-a6ac-1aab7f5c656e@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\0Thu, 2 Nov 2023 08:51:55 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@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> + Kai Huang <kai.huang@intel.com> + 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> + 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 <ackerleytng @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@lists. 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 Thu, Nov 02, 2023, Xiaoyao Li wrote:\n" @@ -17,7 +60,7 @@ "> > 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\n" + "> > [*]https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\n" "> \n" "> I wonder how this CAP is supposed to be checked in userspace, for guest\n" "> memfd case? \n" @@ -50,4 +93,4 @@ "\tif (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO))\n" "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");" -0788b0c17d5f0513043e95cb632ffff9c58f3e0bfab0bc987ee2d9135eb5de4f +25f3190ae9f80a09c831349de9eb8a9d78731b1f10dd0aaf66870c7fcc62f64c
diff --git a/a/1.txt b/N4/1.txt index ec80bef..6dcaa16 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -6,7 +6,7 @@ On Thu, Nov 02, 2023, Xiaoyao Li wrote: > > 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 > > I wonder how this CAP is supposed to be checked in userspace, for guest > memfd case? @@ -38,3 +38,10 @@ supported, i.e. userspace should be able to do: if (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO)) abort("KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ"); + + + +_______________________________________________ +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 3031b8a..f1e6a01 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -4,9 +4,53 @@ "ref\0ZUKMsOdg3N9wmEzy@google.com\0" "ref\033686031-c1df-4ef5-a6ac-1aab7f5c656e@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\0Thu, 2 Nov 2023 08:51:55 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Xiaoyao Li <xiaoyao.li@intel.com>\0" + "Cc\0Kai Huang <kai.huang@intel.com>" + viro@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> + 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 Thu, Nov 02, 2023, Xiaoyao Li wrote:\n" @@ -17,7 +61,7 @@ "> > 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\n" + "> > [*]https://lore.kernel.org/all/20230908222905.1321305-8-amoorthy@google.com\n" "> \n" "> I wonder how this CAP is supposed to be checked in userspace, for guest\n" "> memfd case? \n" @@ -48,6 +92,13 @@ "supported, i.e. userspace should be able to do:\n" "\n" "\tif (!kvm_check_extension(s, KVM_CAP_MEMORY_FAULT_INFO))\n" - "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");" + "\t\tabort(\"KVM_CAP_MEMORY_FAULT_INFO required for fancy feature XYZ\");\n" + "\n" + "\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 -0788b0c17d5f0513043e95cb632ffff9c58f3e0bfab0bc987ee2d9135eb5de4f +ee1124460fdacad4d5fedc6cccbe5517baab3e5cc8c6e0177d46f6d896d3003e
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.