<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/arch/sh/include/asm/mutex-llsc.h, branch dev</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2013-06-26T10:10:55+00:00</updated>
<entry>
<title>arch: Make __mutex_fastpath_lock_retval return whether fastpath succeeded or not</title>
<updated>2013-06-26T10:10:55+00:00</updated>
<author>
<name>Maarten Lankhorst</name>
<email>maarten.lankhorst@canonical.com</email>
</author>
<published>2013-06-20T11:31:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=a41b56efa70e060f650aeb54740aaf52044a1ead'/>
<id>urn:sha1:a41b56efa70e060f650aeb54740aaf52044a1ead</id>
<content type='text'>
This will allow me to call functions that have multiple
arguments if fastpath fails. This is required to support ticket
mutexes, because they need to be able to pass an extra argument
to the fail function.

Originally I duplicated the functions, by adding
__mutex_fastpath_lock_retval_arg. This ended up being just a
duplication of the existing function, so a way to test if
fastpath was called ended up being better.

This also cleaned up the reservation mutex patch some by being
able to call an atomic_set instead of atomic_xchg, and making it
easier to detect if the wrong unlock function was previously
used.

Signed-off-by: Maarten Lankhorst &lt;maarten.lankhorst@canonical.com&gt;
Acked-by: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;
Cc: dri-devel@lists.freedesktop.org
Cc: linaro-mm-sig@lists.linaro.org
Cc: robclark@gmail.com
Cc: rostedt@goodmis.org
Cc: daniel@ffwll.ch
Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Link: http://lkml.kernel.org/r/20130620113105.4001.83929.stgit@patser
Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix up T-bit error handling in SH-4A mutex fastpath.</title>
<updated>2009-01-29T02:56:03+00:00</updated>
<author>
<name>Takashi Yoshii</name>
<email>yoshii.takashi@renesas.com</email>
</author>
<published>2009-01-28T09:29:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c20f326a62c046ee958c3aa584f183201adb229f'/>
<id>urn:sha1:c20f326a62c046ee958c3aa584f183201adb229f</id>
<content type='text'>
This corrects a deadlock encountered on ap325 in the cases where the
mutex is contended and the slow-path needs to be fallen back upon.

Signed-off-by: Takashi YOSHII &lt;yoshii.takashi@renesas.com&gt;
Signed-off-by: Kuninori Morimoto &lt;morimoto.kuninori@renesas.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix an off-by-1 check in __mutex_fastpath_unlock().</title>
<updated>2008-12-22T09:44:02+00:00</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2008-12-08T08:01:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=06be3724548a443a99d703ff79f43d6f1e2975f0'/>
<id>urn:sha1:06be3724548a443a99d703ff79f43d6f1e2975f0</id>
<content type='text'>
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix up the SH-4A mutex fastpath semantics.</title>
<updated>2008-12-22T09:43:52+00:00</updated>
<author>
<name>Paul Mundt</name>
<email>lethal@linux-sh.org</email>
</author>
<published>2008-12-08T02:25:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=77ba93a7ac5fb0d9338bffbf97c787b8efe00806'/>
<id>urn:sha1:77ba93a7ac5fb0d9338bffbf97c787b8efe00806</id>
<content type='text'>
This fixes up the __mutex_fastpath_xxx() routines to match the semantics
noted in the comment. Previously these were looping rather than doing a
single-pass, which is counter-intuitive, as the slow path takes care of
the looping for us in the event of contention.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Add SH-4A optimized fastpath mutex implementation.</title>
<updated>2008-12-22T09:42:55+00:00</updated>
<author>
<name>Michael Trimarchi</name>
<email>trimarchimichael@yahoo.it</email>
</author>
<published>2008-11-25T12:37:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=0c9122323acb0c3410dfbd219cb47f4c2e9305e3'/>
<id>urn:sha1:0c9122323acb0c3410dfbd219cb47f4c2e9305e3</id>
<content type='text'>
Add fast mutex path implementation for the SH4A architecture

Signed-off-by: Michael Trimarchi &lt;trimarchimichael@yahoo.it&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
</feed>
