diff for duplicates of <ZQOmcc969s90DwNz@google.com> diff --git a/a/1.txt b/N1/1.txt index 36311b4..3c26be3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -136,7 +136,7 @@ KVM screws up ASID management, bad things happen to the host, not (just) the gue > If so, then it is fine to bind on creation time, use a VM ioctl > over a system ioctl, and the method of refcounting in gmem v12 is okay. > -> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/ -> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/ +> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/ +> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/ > > > <snip> diff --git a/a/content_digest b/N1/content_digest index 8b0e0f3..ca7bc14 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,9 +3,48 @@ "ref\0ZQNN2AyDJ8dF0/6D@google.com\0" "ref\0diqzv8ccjqbd.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 17:33:53 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + 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-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Thu, Sep 14, 2023, Ackerley Tng wrote:\n" @@ -146,9 +185,9 @@ "> If so, then it is fine to bind on creation time, use a VM ioctl\n" "> over a system ioctl, and the method of refcounting in gmem v12 is okay.\n" "> \n" - "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/\n" - "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/\n" + "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/\n" + "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/\n" "> \n" > > <snip> -364caee12fe63fdc06ef6426070559109b263932381ff5d537738e673376a14a +232e1dffa52c0def0337598261d62c4bfb15a80a711f1073455557bcc5ab506d
diff --git a/a/1.txt b/N2/1.txt index 36311b4..0ca2d1f 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -136,7 +136,12 @@ KVM screws up ASID management, bad things happen to the host, not (just) the gue > If so, then it is fine to bind on creation time, use a VM ioctl > over a system ioctl, and the method of refcounting in gmem v12 is okay. > -> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/ -> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/ +> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/ +> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/ > > > <snip> + +_______________________________________________ +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 8b0e0f3..29029f4 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,9 +3,48 @@ "ref\0ZQNN2AyDJ8dF0/6D@google.com\0" "ref\0diqzv8ccjqbd.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 17:33:53 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + 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-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Thu, Sep 14, 2023, Ackerley Tng wrote:\n" @@ -146,9 +185,14 @@ "> If so, then it is fine to bind on creation time, use a VM ioctl\n" "> over a system ioctl, and the method of refcounting in gmem v12 is okay.\n" "> \n" - "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/\n" - "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/\n" + "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/\n" + "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/\n" "> \n" - > > <snip> + "> > <snip>\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -364caee12fe63fdc06ef6426070559109b263932381ff5d537738e673376a14a +b8d8ae6b863cfd153b947ba8e4fe125be3e9dba934057285733b7a033ff690e1
diff --git a/a/1.txt b/N3/1.txt index 36311b4..3c26be3 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -136,7 +136,7 @@ KVM screws up ASID management, bad things happen to the host, not (just) the gue > If so, then it is fine to bind on creation time, use a VM ioctl > over a system ioctl, and the method of refcounting in gmem v12 is okay. > -> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/ -> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/ +> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/ +> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/ > > > <snip> diff --git a/a/content_digest b/N3/content_digest index 8b0e0f3..bb682f7 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,9 +3,47 @@ "ref\0ZQNN2AyDJ8dF0/6D@google.com\0" "ref\0diqzv8ccjqbd.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 17:33:53 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0kvm@vger.kernel.org" + david@redhat.com + yu.c.zhang@linux.intel.com + linux-kernel@vger.kernel.org + linux-mm@kvack.org + chao.p.peng@linux.intel.com + linux-riscv@lists.infradead.org + isaku.yamahata@gmail.com + paul@paul-moore.com + maz@kernel.org + chenhuacai@kernel.org + jmorris@namei.org + willy@infradead.org + wei.w.wang@intel.com + tabba@google.com + jarkko@kernel.org + serge@hallyn.com + mail@maciej.szmigiero.name + aou@eecs.berkeley.edu + vbabka@suse.cz + michael.roth@amd.com + paul.walmsley@sifive.com + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + qperret@google.com + liam.merwick@oracle.com + linux-mips@vger.kernel.org + oliver.upton@linux.dev + linux-security-module@vger.kernel.org + palmer@dabbelt.com + kvm-riscv@lists.infradead.org + anup@brainfault.org + linux-fsdevel@vger.kernel.org + pbonzini@redhat.com + akpm@linux-foundation.org + vannapurve@google.com + linuxppc-dev@lists.ozlabs.org + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Thu, Sep 14, 2023, Ackerley Tng wrote:\n" @@ -146,9 +184,9 @@ "> If so, then it is fine to bind on creation time, use a VM ioctl\n" "> over a system ioctl, and the method of refcounting in gmem v12 is okay.\n" "> \n" - "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/\n" - "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/\n" + "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/\n" + "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/\n" "> \n" > > <snip> -364caee12fe63fdc06ef6426070559109b263932381ff5d537738e673376a14a +9c8eb5874d4e0ba6d5873b70ca4027da229ba8b6db69eab39591d15b739b2d32
diff --git a/a/1.txt b/N4/1.txt index 36311b4..6daf7dd 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -136,7 +136,12 @@ KVM screws up ASID management, bad things happen to the host, not (just) the gue > If so, then it is fine to bind on creation time, use a VM ioctl > over a system ioctl, and the method of refcounting in gmem v12 is okay. > -> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/ -> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/ +> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/ +> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/ > > > <snip> + +_______________________________________________ +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 8b0e0f3..38e8100 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -3,9 +3,48 @@ "ref\0ZQNN2AyDJ8dF0/6D@google.com\0" "ref\0diqzv8ccjqbd.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Thu, 14 Sep 2023 17:33:53 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + 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-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Thu, Sep 14, 2023, Ackerley Tng wrote:\n" @@ -146,9 +185,14 @@ "> If so, then it is fine to bind on creation time, use a VM ioctl\n" "> over a system ioctl, and the method of refcounting in gmem v12 is okay.\n" "> \n" - "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF at google.com/\n" - "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu at google.com/\n" + "> [1] https://lore.kernel.org/lkml/ZNKv9ul2I7A4V7IF@google.com/\n" + "> [2] https://lore.kernel.org/lkml/ZOO782YGRY0YMuPu@google.com/\n" "> \n" - > > <snip> + "> > <snip>\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 -364caee12fe63fdc06ef6426070559109b263932381ff5d537738e673376a14a +3727030bcefe47243e8f965a32518e35095b7108dd5b501c892e542c09eb6199
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.