diff for duplicates of <Zq00OYowF5kc9QFE@google.com> diff --git a/a/1.txt b/N1/1.txt index 4362cb8..fea5ced 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Fri, Aug 02, 2024, maobibo wrote: -> On 2024/7/27 ??7:52, Sean Christopherson wrote: +> On 2024/7/27 上午7:52, Sean Christopherson wrote: > > Mark pages/folios dirty only the slow page fault path, i.e. only when > > mmu_lock is held and the operation is mmu_notifier-protected, as marking a > > page/folio dirty after it has been written back can make some filesystems @@ -8,7 +8,7 @@ On Fri, Aug 02, 2024, maobibo wrote: > > > > See the link below for details. > > -> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com +> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com > > Signed-off-by: Sean Christopherson <seanjc@google.com> > > --- > > arch/loongarch/kvm/mmu.c | 18 ++++++++++-------- diff --git a/a/content_digest b/N1/content_digest index 005ec7f..db36440 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,13 +2,37 @@ "ref\020240726235234.228822-65-seanjc@google.com\0" "ref\0a039b758-d4e3-3798-806f-25bceb2f33a5@loongson.cn\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" + "Subject\0Re: [PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" "Date\0Fri, 2 Aug 2024 12:32:09 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0maobibo <maobibo@loongson.cn>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Tianrui Zhao <zhaotianrui@loongson.cn> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Christian Borntraeger <borntraeger@linux.ibm.com> + Janosch Frank <frankja@linux.ibm.com> + Claudio Imbrenda <imbrenda@linux.ibm.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + loongarch@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-kernel@vger.kernel.org + David Matlack <dmatlack@google.com> + " David Stevens <stevensd@chromium.org>\0" "\00:1\0" "b\0" "On Fri, Aug 02, 2024, maobibo wrote:\n" - "> On 2024/7/27 ??7:52, Sean Christopherson wrote:\n" + "> On 2024/7/27 \344\270\212\345\215\2107:52, Sean Christopherson wrote:\n" "> > Mark pages/folios dirty only the slow page fault path, i.e. only when\n" "> > mmu_lock is held and the operation is mmu_notifier-protected, as marking a\n" "> > page/folio dirty after it has been written back can make some filesystems\n" @@ -17,7 +41,7 @@ "> > \n" "> > See the link below for details.\n" "> > \n" - "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com\n" + "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com\n" "> > Signed-off-by: Sean Christopherson <seanjc@google.com>\n" "> > ---\n" "> > arch/loongarch/kvm/mmu.c | 18 ++++++++++--------\n" @@ -64,4 +88,4 @@ "an mmu_notifier invalidation. I.e. if the page is mapped writable in KVM's\n" stage-2 PTEs, then its folio has already been marked dirty. -3670b220edc59bc9cf9490fee217cb19c8a671eef887778002333062fe5545dd +896a5e45a03782b57e960420000b7c244c3cd53b65686f70e72bcb7147a51b92
diff --git a/a/1.txt b/N2/1.txt index 4362cb8..456b45e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On Fri, Aug 02, 2024, maobibo wrote: -> On 2024/7/27 ??7:52, Sean Christopherson wrote: +> On 2024/7/27 上午7:52, Sean Christopherson wrote: > > Mark pages/folios dirty only the slow page fault path, i.e. only when > > mmu_lock is held and the operation is mmu_notifier-protected, as marking a > > page/folio dirty after it has been written back can make some filesystems @@ -8,7 +8,7 @@ On Fri, Aug 02, 2024, maobibo wrote: > > > > See the link below for details. > > -> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com +> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com > > Signed-off-by: Sean Christopherson <seanjc@google.com> > > --- > > arch/loongarch/kvm/mmu.c | 18 ++++++++++-------- @@ -54,3 +54,8 @@ Practically speaking, I'm 99.9% certain it doesn't matter. The folio is marked dirty by core MM when the folio is made writable, and cleaning the folio triggers an mmu_notifier invalidation. I.e. if the page is mapped writable in KVM's stage-2 PTEs, then its folio has already been marked dirty. + +_______________________________________________ +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 005ec7f..78a7dfc 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,13 +2,37 @@ "ref\020240726235234.228822-65-seanjc@google.com\0" "ref\0a039b758-d4e3-3798-806f-25bceb2f33a5@loongson.cn\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" + "Subject\0Re: [PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" "Date\0Fri, 2 Aug 2024 12:32:09 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0maobibo <maobibo@loongson.cn>\0" + "Cc\0Paolo Bonzini <pbonzini@redhat.com>" + Marc Zyngier <maz@kernel.org> + Oliver Upton <oliver.upton@linux.dev> + Tianrui Zhao <zhaotianrui@loongson.cn> + Huacai Chen <chenhuacai@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Anup Patel <anup@brainfault.org> + Paul Walmsley <paul.walmsley@sifive.com> + Palmer Dabbelt <palmer@dabbelt.com> + Albert Ou <aou@eecs.berkeley.edu> + Christian Borntraeger <borntraeger@linux.ibm.com> + Janosch Frank <frankja@linux.ibm.com> + Claudio Imbrenda <imbrenda@linux.ibm.com> + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + loongarch@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-kernel@vger.kernel.org + David Matlack <dmatlack@google.com> + " David Stevens <stevensd@chromium.org>\0" "\00:1\0" "b\0" "On Fri, Aug 02, 2024, maobibo wrote:\n" - "> On 2024/7/27 ??7:52, Sean Christopherson wrote:\n" + "> On 2024/7/27 \344\270\212\345\215\2107:52, Sean Christopherson wrote:\n" "> > Mark pages/folios dirty only the slow page fault path, i.e. only when\n" "> > mmu_lock is held and the operation is mmu_notifier-protected, as marking a\n" "> > page/folio dirty after it has been written back can make some filesystems\n" @@ -17,7 +41,7 @@ "> > \n" "> > See the link below for details.\n" "> > \n" - "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com\n" + "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com\n" "> > Signed-off-by: Sean Christopherson <seanjc@google.com>\n" "> > ---\n" "> > arch/loongarch/kvm/mmu.c | 18 ++++++++++--------\n" @@ -62,6 +86,11 @@ "Practically speaking, I'm 99.9% certain it doesn't matter. The folio is marked\n" "dirty by core MM when the folio is made writable, and cleaning the folio triggers\n" "an mmu_notifier invalidation. I.e. if the page is mapped writable in KVM's\n" - stage-2 PTEs, then its folio has already been marked dirty. + "stage-2 PTEs, then its folio has already been marked dirty.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -3670b220edc59bc9cf9490fee217cb19c8a671eef887778002333062fe5545dd +556d2c4667eed232440567ef625b1e797efb057b5e27dca42e51182dedca1311
diff --git a/a/1.txt b/N3/1.txt index 4362cb8..fea5ced 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,5 +1,5 @@ On Fri, Aug 02, 2024, maobibo wrote: -> On 2024/7/27 ??7:52, Sean Christopherson wrote: +> On 2024/7/27 上午7:52, Sean Christopherson wrote: > > Mark pages/folios dirty only the slow page fault path, i.e. only when > > mmu_lock is held and the operation is mmu_notifier-protected, as marking a > > page/folio dirty after it has been written back can make some filesystems @@ -8,7 +8,7 @@ On Fri, Aug 02, 2024, maobibo wrote: > > > > See the link below for details. > > -> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com +> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com > > Signed-off-by: Sean Christopherson <seanjc@google.com> > > --- > > arch/loongarch/kvm/mmu.c | 18 ++++++++++-------- diff --git a/a/content_digest b/N3/content_digest index 005ec7f..dd677a6 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,13 +2,36 @@ "ref\020240726235234.228822-65-seanjc@google.com\0" "ref\0a039b758-d4e3-3798-806f-25bceb2f33a5@loongson.cn\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" + "Subject\0Re: [PATCH v12 64/84] KVM: LoongArch: Mark \"struct page\" pfns dirty only in \"slow\" page fault path\0" "Date\0Fri, 2 Aug 2024 12:32:09 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0maobibo <maobibo@loongson.cn>\0" + "Cc\0kvm@vger.kernel.org" + linux-kernel@vger.kernel.org + David Matlack <dmatlack@google.com> + linux-riscv@lists.infradead.org + Claudio Imbrenda <imbrenda@linux.ibm.com> + Marc Zyngier <maz@kernel.org> + Janosch Frank <frankja@linux.ibm.com> + Huacai Chen <chenhuacai@kernel.org> + Christian Borntraeger <borntraeger@linux.ibm.com> + Albert Ou <aou@eecs.berkeley.edu> + loongarch@lists.linux.dev + Paul Walmsley <paul.walmsley@sifive.com> + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + linux-mips@vger.kernel.org + Oliver Upton <oliver.upton@linux.dev> + Palmer Dabbelt <palmer@dabbelt.com> + David Stevens <stevensd@chromium.org> + kvm-riscv@lists.infradead.org + Anup Patel <anup@brainfault.org> + Paolo Bonzini <pbonzini@redhat.com> + Tianrui Zhao <zhaotianrui@loongson.cn> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On Fri, Aug 02, 2024, maobibo wrote:\n" - "> On 2024/7/27 ??7:52, Sean Christopherson wrote:\n" + "> On 2024/7/27 \344\270\212\345\215\2107:52, Sean Christopherson wrote:\n" "> > Mark pages/folios dirty only the slow page fault path, i.e. only when\n" "> > mmu_lock is held and the operation is mmu_notifier-protected, as marking a\n" "> > page/folio dirty after it has been written back can make some filesystems\n" @@ -17,7 +40,7 @@ "> > \n" "> > See the link below for details.\n" "> > \n" - "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes at gmail.com\n" + "> > Link: https://lore.kernel.org/all/cover.1683044162.git.lstoakes@gmail.com\n" "> > Signed-off-by: Sean Christopherson <seanjc@google.com>\n" "> > ---\n" "> > arch/loongarch/kvm/mmu.c | 18 ++++++++++--------\n" @@ -64,4 +87,4 @@ "an mmu_notifier invalidation. I.e. if the page is mapped writable in KVM's\n" stage-2 PTEs, then its folio has already been marked dirty. -3670b220edc59bc9cf9490fee217cb19c8a671eef887778002333062fe5545dd +0444a661f92bf4da5f90aadd79388d300b8049671bc3e18ef686b72240982cd7
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.