diff for duplicates of <Zl5eat0sh7rrspUG@google.com> diff --git a/a/1.txt b/N1/1.txt index 830aef6..1759ff3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Mon, Jun 03, 2024, James Houghton wrote: -> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote: +> On Mon, Jun 3, 2024 at 4:03 PM Sean Christopherson <seanjc@google.com> wrote: > > But before we do that, I think we need to perform due dilegence (or provide data) > > showing that having KVM take mmu_lock for write in the "fast only" API provides > > better total behavior. I.e. that the additional accuracy is indeed worth the cost. diff --git a/a/content_digest b/N1/content_digest index cef72f4..9d989a6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,13 +9,54 @@ "ref\0Zl5LqcusZ88QOGQY@google.com\0" "ref\0CADrL8HU734C_OQhzszWJWMXEXLN6HkBo4yweN2fX4BbOegXrFA@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" + "Subject\0Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" "Date\0Mon, 3 Jun 2024 17:23:06 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0James Houghton <jthoughton@google.com>\0" + "Cc\0Yu Zhao <yuzhao@google.com>" + Andrew Morton <akpm@linux-foundation.org> + Paolo Bonzini <pbonzini@redhat.com> + Albert Ou <aou@eecs.berkeley.edu> + Ankit Agrawal <ankita@nvidia.com> + Anup Patel <anup@brainfault.org> + Atish Patra <atishp@atishpatra.org> + Axel Rasmussen <axelrasmussen@google.com> + Bibo Mao <maobibo@loongson.cn> + Catalin Marinas <catalin.marinas@arm.com> + David Matlack <dmatlack@google.com> + David Rientjes <rientjes@google.com> + Huacai Chen <chenhuacai@kernel.org> + James Morse <james.morse@arm.com> + Jonathan Corbet <corbet@lwn.net> + Marc Zyngier <maz@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Nicholas Piggin <npiggin@gmail.com> + Oliver Upton <oliver.upton@linux.dev> + Palmer Dabbelt <palmer@dabbelt.com> + Paul Walmsley <paul.walmsley@sifive.com> + Raghavendra Rao Ananta <rananta@google.com> + Ryan Roberts <ryan.roberts@arm.com> + Shaoqin Huang <shahuang@redhat.com> + Shuah Khan <shuah@kernel.org> + Suzuki K Poulose <suzuki.poulose@arm.com> + Tianrui Zhao <zhaotianrui@loongson.cn> + Will Deacon <will@kernel.org> + Zenghui Yu <yuzenghui@huawei.com> + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + linux-doc@vger.kernel.org + linux-kernel@vger.kernel.org + linux-kselftest@vger.kernel.org + linux-mips@vger.kernel.org + linux-mm@kvack.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + " loongarch@lists.linux.dev\0" "\00:1\0" "b\0" "On Mon, Jun 03, 2024, James Houghton wrote:\n" - "> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Mon, Jun 3, 2024 at 4:03\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > But before we do that, I think we need to perform due dilegence (or provide data)\n" "> > showing that having KVM take mmu_lock for write in the \"fast only\" API provides\n" "> > better total behavior. I.e. that the additional accuracy is indeed worth the cost.\n" @@ -29,4 +70,4 @@ "enabled. If the test fails because that doesn't hold true, then we _want_ the\n" failure. -d56e330acc5c59e8d99337878a79e55ab7c99365eb9df10bb45e7869cddc9f23 +40ec4d20d16f2714ff847cc900f902dff4c88eab24b66c30e71a1dd798d9e142
diff --git a/a/1.txt b/N2/1.txt index 830aef6..0b5cb2f 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On Mon, Jun 03, 2024, James Houghton wrote: -> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote: +> On Mon, Jun 3, 2024 at 4:03 PM Sean Christopherson <seanjc@google.com> wrote: > > But before we do that, I think we need to perform due dilegence (or provide data) > > showing that having KVM take mmu_lock for write in the "fast only" API provides > > better total behavior. I.e. that the additional accuracy is indeed worth the cost. @@ -12,3 +12,8 @@ Enable it only on architectures+setups that are guaranteed to implement the fast-only API? E.g. on x86, it darn well better be active if the TDP MMU is enabled. If the test fails because that doesn't hold true, then we _want_ the failure. + +_______________________________________________ +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 cef72f4..02d39e6 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -9,13 +9,54 @@ "ref\0Zl5LqcusZ88QOGQY@google.com\0" "ref\0CADrL8HU734C_OQhzszWJWMXEXLN6HkBo4yweN2fX4BbOegXrFA@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" + "Subject\0Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" "Date\0Mon, 3 Jun 2024 17:23:06 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0James Houghton <jthoughton@google.com>\0" + "Cc\0Yu Zhao <yuzhao@google.com>" + Andrew Morton <akpm@linux-foundation.org> + Paolo Bonzini <pbonzini@redhat.com> + Albert Ou <aou@eecs.berkeley.edu> + Ankit Agrawal <ankita@nvidia.com> + Anup Patel <anup@brainfault.org> + Atish Patra <atishp@atishpatra.org> + Axel Rasmussen <axelrasmussen@google.com> + Bibo Mao <maobibo@loongson.cn> + Catalin Marinas <catalin.marinas@arm.com> + David Matlack <dmatlack@google.com> + David Rientjes <rientjes@google.com> + Huacai Chen <chenhuacai@kernel.org> + James Morse <james.morse@arm.com> + Jonathan Corbet <corbet@lwn.net> + Marc Zyngier <maz@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Nicholas Piggin <npiggin@gmail.com> + Oliver Upton <oliver.upton@linux.dev> + Palmer Dabbelt <palmer@dabbelt.com> + Paul Walmsley <paul.walmsley@sifive.com> + Raghavendra Rao Ananta <rananta@google.com> + Ryan Roberts <ryan.roberts@arm.com> + Shaoqin Huang <shahuang@redhat.com> + Shuah Khan <shuah@kernel.org> + Suzuki K Poulose <suzuki.poulose@arm.com> + Tianrui Zhao <zhaotianrui@loongson.cn> + Will Deacon <will@kernel.org> + Zenghui Yu <yuzenghui@huawei.com> + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + linux-doc@vger.kernel.org + linux-kernel@vger.kernel.org + linux-kselftest@vger.kernel.org + linux-mips@vger.kernel.org + linux-mm@kvack.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + " loongarch@lists.linux.dev\0" "\00:1\0" "b\0" "On Mon, Jun 03, 2024, James Houghton wrote:\n" - "> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Mon, Jun 3, 2024 at 4:03\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > But before we do that, I think we need to perform due dilegence (or provide data)\n" "> > showing that having KVM take mmu_lock for write in the \"fast only\" API provides\n" "> > better total behavior. I.e. that the additional accuracy is indeed worth the cost.\n" @@ -27,6 +68,11 @@ "Enable it only on architectures+setups that are guaranteed to implement the\n" "fast-only API? E.g. on x86, it darn well better be active if the TDP MMU is\n" "enabled. If the test fails because that doesn't hold true, then we _want_ the\n" - failure. + "failure.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -d56e330acc5c59e8d99337878a79e55ab7c99365eb9df10bb45e7869cddc9f23 +2c7abb735acad6d4b3c95cde33afd6ff2980df7b295e57c0c300c12e93f98764
diff --git a/a/1.txt b/N3/1.txt index 830aef6..1759ff3 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,5 +1,5 @@ On Mon, Jun 03, 2024, James Houghton wrote: -> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote: +> On Mon, Jun 3, 2024 at 4:03 PM Sean Christopherson <seanjc@google.com> wrote: > > But before we do that, I think we need to perform due dilegence (or provide data) > > showing that having KVM take mmu_lock for write in the "fast only" API provides > > better total behavior. I.e. that the additional accuracy is indeed worth the cost. diff --git a/a/content_digest b/N3/content_digest index cef72f4..1a026e3 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -9,13 +9,53 @@ "ref\0Zl5LqcusZ88QOGQY@google.com\0" "ref\0CADrL8HU734C_OQhzszWJWMXEXLN6HkBo4yweN2fX4BbOegXrFA@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" + "Subject\0Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" "Date\0Mon, 3 Jun 2024 17:23:06 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0James Houghton <jthoughton@google.com>\0" + "Cc\0kvm@vger.kernel.org" + linux-doc@vger.kernel.org + Catalin Marinas <catalin.marinas@arm.com> + Atish Patra <atishp@atishpatra.org> + linux-kernel@vger.kernel.org + kvmarm@lists.linux.dev + linux-kselftest@vger.kernel.org + Raghavendra Rao Ananta <rananta@google.com> + linux-riscv@lists.infradead.org + Shuah Khan <shuah@kernel.org> + Yu Zhao <yuzhao@google.com> + Jonathan Corbet <corbet@lwn.net> + Anup Patel <anup@brainfault.org> + Huacai Chen <chenhuacai@kernel.org> + David Rientjes <rientjes@google.com> + Zenghui Yu <yuzenghui@huawei.com> + Axel Rasmussen <axelrasmussen@google.com> + linux-mips@vger.kernel.org + Albert Ou <aou@eecs.berkeley.edu> + Ryan Roberts <ryan.roberts@arm.com> + Will Deacon <will@kernel.org> + Suzuki K Poulose <suzuki.poulose@arm.com> + Shaoqin Huang <shahuang@redhat.com> + Nicholas Piggin <npiggin@gmail.com> + Bibo Mao <maobibo@loongson.cn> + loongarch@lists.linux.dev + Paul Walmsley <paul.walmsley@sifive.com> + David Matlack <dmatlack@google.com> + Palmer Dabbelt <palmer@dabbelt.com > + linux-arm-kernel@lists.infradead.org + linux-mm@kvack.org + Ankit Agrawal <ankita@nvidia.com> + Oliver Upton <oliver.upton@linux.dev> + James Morse <james.morse@arm.com> + kvm-riscv@lists.infradead.org + Marc Zyngier <maz@kernel.org> + Paolo Bonzini <pbonzini@redhat.com> + Andrew Morton <akpm@linux-foundation.org> + Tianrui Zhao <zhaotianrui@loongson.cn> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On Mon, Jun 03, 2024, James Houghton wrote:\n" - "> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Mon, Jun 3, 2024 at 4:03\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > But before we do that, I think we need to perform due dilegence (or provide data)\n" "> > showing that having KVM take mmu_lock for write in the \"fast only\" API provides\n" "> > better total behavior. I.e. that the additional accuracy is indeed worth the cost.\n" @@ -29,4 +69,4 @@ "enabled. If the test fails because that doesn't hold true, then we _want_ the\n" failure. -d56e330acc5c59e8d99337878a79e55ab7c99365eb9df10bb45e7869cddc9f23 +de00fd43869d8ae468c1a5a4faf09fe335e92061b521bf9d13a9092c1c27f124
diff --git a/a/1.txt b/N4/1.txt index 830aef6..d04e238 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -1,5 +1,5 @@ On Mon, Jun 03, 2024, James Houghton wrote: -> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote: +> On Mon, Jun 3, 2024 at 4:03 PM Sean Christopherson <seanjc@google.com> wrote: > > But before we do that, I think we need to perform due dilegence (or provide data) > > showing that having KVM take mmu_lock for write in the "fast only" API provides > > better total behavior. I.e. that the additional accuracy is indeed worth the cost. @@ -12,3 +12,8 @@ Enable it only on architectures+setups that are guaranteed to implement the fast-only API? E.g. on x86, it darn well better be active if the TDP MMU is enabled. If the test fails because that doesn't hold true, then we _want_ the failure. + +_______________________________________________ +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 cef72f4..31f2a54 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -9,13 +9,54 @@ "ref\0Zl5LqcusZ88QOGQY@google.com\0" "ref\0CADrL8HU734C_OQhzszWJWMXEXLN6HkBo4yweN2fX4BbOegXrFA@mail.gmail.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" + "Subject\0Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging\0" "Date\0Mon, 3 Jun 2024 17:23:06 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0James Houghton <jthoughton@google.com>\0" + "Cc\0Yu Zhao <yuzhao@google.com>" + Andrew Morton <akpm@linux-foundation.org> + Paolo Bonzini <pbonzini@redhat.com> + Albert Ou <aou@eecs.berkeley.edu> + Ankit Agrawal <ankita@nvidia.com> + Anup Patel <anup@brainfault.org> + Atish Patra <atishp@atishpatra.org> + Axel Rasmussen <axelrasmussen@google.com> + Bibo Mao <maobibo@loongson.cn> + Catalin Marinas <catalin.marinas@arm.com> + David Matlack <dmatlack@google.com> + David Rientjes <rientjes@google.com> + Huacai Chen <chenhuacai@kernel.org> + James Morse <james.morse@arm.com> + Jonathan Corbet <corbet@lwn.net> + Marc Zyngier <maz@kernel.org> + Michael Ellerman <mpe@ellerman.id.au> + Nicholas Piggin <npiggin@gmail.com> + Oliver Upton <oliver.upton@linux.dev> + Palmer Dabbelt <palmer@dabbelt.com> + Paul Walmsley <paul.walmsley@sifive.com> + Raghavendra Rao Ananta <rananta@google.com> + Ryan Roberts <ryan.roberts@arm.com> + Shaoqin Huang <shahuang@redhat.com> + Shuah Khan <shuah@kernel.org> + Suzuki K Poulose <suzuki.poulose@arm.com> + Tianrui Zhao <zhaotianrui@loongson.cn> + Will Deacon <will@kernel.org> + Zenghui Yu <yuzenghui@huawei.com> + kvm-riscv@lists.infradead.org + kvm@vger.kernel.org + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + linux-doc@vger.kernel.org + linux-kernel@vger.kernel.org + linux-kselftest@vger.kernel.org + linux-mips@vger.kernel.org + linux-mm@kvack.org + linux-riscv@lists.infradead.org + linuxppc-dev@lists.ozlabs.org + " loongarch@lists.linux.dev\0" "\00:1\0" "b\0" "On Mon, Jun 03, 2024, James Houghton wrote:\n" - "> On Mon, Jun 3, 2024 at 4:03?PM Sean Christopherson <seanjc@google.com> wrote:\n" + "> On Mon, Jun 3, 2024 at 4:03\342\200\257PM Sean Christopherson <seanjc@google.com> wrote:\n" "> > But before we do that, I think we need to perform due dilegence (or provide data)\n" "> > showing that having KVM take mmu_lock for write in the \"fast only\" API provides\n" "> > better total behavior. I.e. that the additional accuracy is indeed worth the cost.\n" @@ -27,6 +68,11 @@ "Enable it only on architectures+setups that are guaranteed to implement the\n" "fast-only API? E.g. on x86, it darn well better be active if the TDP MMU is\n" "enabled. If the test fails because that doesn't hold true, then we _want_ the\n" - failure. + "failure.\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 -d56e330acc5c59e8d99337878a79e55ab7c99365eb9df10bb45e7869cddc9f23 +c175914bd691270e14a44c3ffe4551320bf4bbadad238b93ea906dd05a88fe11
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.