[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cfb25527-01fc-d51f-b4fb-ea1a6cb90c99@redhat.com>
Date: Wed, 30 Jan 2019 11:25:25 -0500
From: Waiman Long <longman@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...hat.com>, Will Deacon <will.deacon@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, x86@...nel.org,
Zhenzhong Duan <zhenzhong.duan@...cle.com>,
James Morse <james.morse@....com>,
SRINIVAS <srinivas.eeda@...cle.com>
Subject: Re: [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels
On 01/30/2019 09:07 AM, Peter Zijlstra wrote:
>> Waiman Long (4):
>> locking/qspinlock: Handle > 4 slowpath nesting levels
>> locking/qspinlock_stat: Track the no MCS node available case
> I've taken these two,
>
>> locking/qspinlock_stat: Introduce a generic lockevent counting APIs
>> locking/lock_events: Make lock_events available for all archs & other
>> locks
> while no real objection to these; I feel we should wait until there are
> in fact more users of this.
I am actually working on a rwsem patch which I plan to use the event
counting for my testing purpose. I will include this two patches in my
patch series.
Thanks,
Longman
Powered by blists - more mailing lists