[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZabqkZ2vXaicy3pZ@duo.ucw.cz>
Date: Tue, 16 Jan 2024 21:44:01 +0100
From: Pavel Machek <pavel@...x.de>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
"Borislav Petkov (AMD)" <bp@...en8.de>, tglx@...utronix.de,
mingo@...hat.com, dave.hansen@...ux.intel.com, x86@...nel.org,
puwen@...on.cn, seanjc@...gle.com, kim.phillips@....com,
reinette.chatre@...el.com, babu.moger@....com, jmattson@...gle.com,
peterz@...radead.org, ashok.raj@...el.com,
rick.p.edgecombe@...el.com, brgerst@...il.com, mjguzik@...il.com,
jpoimboe@...nel.org, nik.borisov@...e.com, aik@....com,
vegard.nossum@...cle.com, daniel.sneddon@...ux.intel.com,
acdunlap@...gle.com
Subject: Re: [PATCH AUTOSEL 5.10 09/10] x86/barrier: Do not serialize MSR
accesses on AMD
Hi!
> From: "Borislav Petkov (AMD)" <bp@...en8.de>
>
> [ Upstream commit 04c3024560d3a14acd18d0a51a1d0a89d29b7eb5 ]
>
> AMD does not have the requirement for a synchronization barrier when
> acccessing a certain group of MSRs. Do not incur that unnecessary
> penalty there.
...
> Performance captured using an unmodified ipi-bench using the 'mesh-ipi' option
> with and without weak_wrmsr_fence() on a Zen4 system also showed significant
> performance improvement without weak_wrmsr_fence(). The 'mesh-ipi' option ignores
> CCX or CCD and just picks random vCPU.
>
> Average throughput (10 iterations) with weak_wrmsr_fence(),
> Cumulative throughput: 4933374 IPI/s
>
> Average throughput (10 iterations) without weak_wrmsr_fence(),
> Cumulative throughput: 6355156 IPI/s
>
> [1] https://github.com/bytedance/kvm-utils/tree/master/microbenchmark/ipi-bench
Speed improvement, not a bugfix. Please drop.
BR,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists