[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1471539134.28391.64.camel@intel.com>
Date: Thu, 18 Aug 2016 19:52:14 +0300
From: Imre Deak <imre.deak@...el.com>
To: Peter Zijlstra <peterz@...radead.org>,
Waiman Long <waiman.long@....com>
Cc: Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ding Tianhong <dingtianhong@...wei.com>,
Jason Low <jason.low2@....com>,
Davidlohr Bueso <dave@...olabs.net>,
"Paul E. McKenney" <paulmck@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Will Deacon <Will.Deacon@....com>,
Tim Chen <tim.c.chen@...ux.intel.com>
Subject: Re: [PATCH v5 3/3] locking/mutex: Ensure forward progress of
waiter-spinner
On to, 2016-08-18 at 17:58 +0200, Peter Zijlstra wrote:
> On Thu, Aug 11, 2016 at 11:01:27AM -0400, Waiman Long wrote:
> > The following is the updated patch that should fix the build error
> > in
> > non-x86 platform.
> >
>
> This patch was whitespace challenged, but I think I munged it
> properly.
>
> I've also stuck something based on Jason's patch on top. Please have
> a
> look at:
>
> https://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/log/?
> h=locking/core
>
> compile tested only so far..
It works for me and fixes my test case.
Nitpick: "Try-acquire now that we got woken at the head of the queue."
would be more accurate by also adding "or received a signal."
--Imre
Powered by blists - more mailing lists