[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172433664072.3702537.8419277728828269501.b4-ty@kernel.org>
Date: Thu, 22 Aug 2024 15:25:08 +0100
From: Marc Zyngier <maz@...nel.org>
To: kvm@...r.kernel.org,
Colton Lewis <coltonlewis@...gle.com>
Cc: Oliver Upton <oliver.upton@...ux.dev>,
Ricardo Koller <ricarkol@...gle.com>,
James Morse <james.morse@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v2] KVM: arm64: Move data barrier to end of split walk
On Thu, 08 Aug 2024 17:42:43 +0000, Colton Lewis wrote:
> This DSB guarantees page table updates have been made visible to the
> hardware table walker. Moving the DSB from stage2_split_walker() to
> after the walk is finished in kvm_pgtable_stage2_split() results in a
> roughly 70% reduction in Clear Dirty Log Time in
> dirty_log_perf_test (modified to use eager page splitting) when using
> huge pages. This gain holds steady through a range of vcpus
> used (tested 1-64) and memory used (tested 1-64GB).
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Move data barrier to end of split walk
commit: 38753cbc4dca431d4354319c7481f6bd1a212baf
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists