locking/mutexes: Standardize arguments in lock/unlock slowpaths
locking/mutexes: Standardize arguments in lock/unlock slowpaths

Just how the locking-end behaves, when unlocking, go ahead and
obtain the proper data structure immediately after the previous
(asm-end) call exits and there are (probably) pending waiters.
This simplifies a bit some of the layering.

Signed-off-by: Davidlohr Bueso <4aa5652442886f3c4e77d3a743dc27e129c1613f@hp.com>
Signed-off-by: Peter Zijlstra <3fddac958924aef220f202ca567388ddab3f14a8@infradead.org>
Cc: 09ebf12aa4fd61769490ade56a7655bcf429b765@hp.com
Cc: bfa14955daca93db2acc6116543d4fa46c7a22b5@hp.com
Cc: 9dbbbf0688fedc85ad4da37637f1a64b8c718ee2@kernel.org
Cc: Linus Torvalds <69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org>
Cc: 2578944098299abf708b08eff6fcf60565553586@vger.kernel.org
Link: http://lkml.kernel.org/r/1406752916-3341-1-git-send-email-4aa5652442886f3c4e77d3a743dc27e129c1613f@hp.com
Signed-off-by: Ingo Molnar <9dbbbf0688fedc85ad4da37637f1a64b8c718ee2@kernel.org>

KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs,KristFoundation/Programs