[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34d86c3a1cd044f28f70202292e1d13a@intel.com>
Date: Wed, 2 Dec 2020 20:36:11 +0000
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
"Luck, Tony" <tony.luck@...el.com>,
Randy Dunlap <rdunlap@...radead.org>,
"Li, Xiaoyao" <xiaoyao.li@...el.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>
CC: linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: RE: [PATCH v4 0/4] x86/bus_lock: Enable bus lock detection
Hi, Dear maintainers,
> A bus lock [1] is acquired through either split locked access to writeback (WB)
> memory or any locked access to non-WB memory. This is typically >1000
> cycles slower than an atomic operation within a cache line. It also disrupts
> performance on other cores.
...
> Change Log:
> v4:
> - Fix a ratelimit wording issue in the doc (Randy).
> - Patch 4 is acked by Randy (Randy).
Friendly reminder about this series...
Thank you very much in advance for your time!
-Fenghua
Powered by blists - more mailing lists