lkml.org 
[lkml]   [2015]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Commit 81a43adae3b9 (locking/mutex: Use acquire/release semantics) causing failures on arm64 (ThunderX)
On Mon, Dec 14, 2015 at 06:49:31PM +0000, One Thousand Gnomes wrote:
>
> But seriously are there any cases we actually care about this for osq ?

So I think what PaulMck is worried about is that one would expect things
like:

mutex_lock();
MMIO(++var);
mutex_unlock();

(the same example Linus gave but with a mutex instead of a spinlock) to
just work.

Now, I haven't checked the code, but I'm not sure we ever rely on osq to
provide the mutex ACQUIRE barrier, since we always need to acquire the
mutex variable itself after we've acquired the osq 'lock'.



\
 
 \ /
  Last update: 2015-12-14 22:01    [W:0.280 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site