<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/arch, branch v2.6.32.23</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/arch?h=v2.6.32.23</id>
<link rel='self' href='https://git.amat.us/linux/atom/arch?h=v2.6.32.23'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-09-27T00:21:43Z</updated>
<entry>
<title>x86: Add memory modify constraints to xchg() and cmpxchg()</title>
<updated>2010-09-27T00:21:43Z</updated>
<author>
<name>H. Peter Anvin</name>
<email>hpa@zytor.com</email>
</author>
<published>2010-07-28T00:01:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a1a34b6cceb66a843dfbec0a197b0067fe9a8dc9'/>
<id>urn:sha1:a1a34b6cceb66a843dfbec0a197b0067fe9a8dc9</id>
<content type='text'>
commit 113fc5a6e8c2288619ff7e8187a6f556b7e0d372 upstream.

[ Backport to .32 by Tomáš Janoušek &lt;tomi@nomi.cz&gt; ]

xchg() and cmpxchg() modify their memory operands, not merely read
them.  For some versions of gcc the "memory" clobber has apparently
dealt with the situation, but not for all.

Originally-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: H. Peter Anvin &lt;hpa@zytor.com&gt;
Cc: Glauber Costa &lt;glommer@redhat.com&gt;
Cc: Avi Kivity &lt;avi@redhat.com&gt;
Cc: Peter Palfrader &lt;peter@palfrader.org&gt;
Cc: Greg KH &lt;gregkh@suse.de&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: Zachary Amsden &lt;zamsden@redhat.com&gt;
Cc: Marcelo Tosatti &lt;mtosatti@redhat.com&gt;
LKML-Reference: &lt;4C4F7277.8050306@zytor.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>alpha: Fix printk format errors</title>
<updated>2010-09-27T00:21:43Z</updated>
<author>
<name>Michael Cree</name>
<email>mcree@orcon.net.nz</email>
</author>
<published>2010-09-01T15:25:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d881186be461f3ccea69fe93f674e3266db7336'/>
<id>urn:sha1:5d881186be461f3ccea69fe93f674e3266db7336</id>
<content type='text'>
commit 3e073367a57d41e506f20aebb98e308387ce3090 upstream.

When compiling alpha generic build get errors such as:
arch/alpha/kernel/err_marvel.c: In function ‘marvel_print_err_cyc’:
arch/alpha/kernel/err_marvel.c:119: error: format ‘%ld’ expects type ‘long int’, but argument 6 has type ‘u64’

Replaced a number of %ld format specifiers with %lld since u64
is unsigned long long.

Signed-off-by: Michael Cree &lt;mcree@orcon.net.nz&gt;
Signed-off-by: Matt Turner &lt;mattst88@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>MIPS: Sibyte: Fix M3 TLB exception handler workaround.</title>
<updated>2010-09-27T00:21:40Z</updated>
<author>
<name>Ralf Baechle</name>
<email>ralf@linux-mips.org</email>
</author>
<published>2010-03-23T16:56:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6d607033481c7031e5fbfe9750542deb52e9b94c'/>
<id>urn:sha1:6d607033481c7031e5fbfe9750542deb52e9b94c</id>
<content type='text'>
commit 3d45285dd1ff4d4a1361b95e2d6508579a4402b5 upstream.

The M3 workaround needs to cmpare the region and VPN2 fields only.

Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>MIPS: uasm: Add OR instruction.</title>
<updated>2010-09-27T00:21:39Z</updated>
<author>
<name>Ralf Baechle</name>
<email>ralf@linux-mips.org</email>
</author>
<published>2010-03-23T14:54:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=606fa05a76966af96cb3c170e6d09b65194e97c9'/>
<id>urn:sha1:606fa05a76966af96cb3c170e6d09b65194e97c9</id>
<content type='text'>
commit 5808184f1b2fe06ef8a54a2b7fb1596d58098acf upstream.

This is needed for the fix of the M3 workaround.

Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
[Backported by Aurelien Jarno &lt;aurelien@aurel32.net&gt;]
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>MIPS: Set io_map_base for several PCI bridges lacking it</title>
<updated>2010-09-27T00:21:39Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2010-06-13T21:22:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a4d6b59efe59fc769e2d55292653922cb23c41c7'/>
<id>urn:sha1:a4d6b59efe59fc769e2d55292653922cb23c41c7</id>
<content type='text'>
commit 8faf2e6c201d95b780cd3b4674b7a55ede6dcbbb upstream.

Several MIPS platforms don't set pci_controller::io_map_base for their
PCI bridges.  This results in a panic in pci_iomap().  (The panic is
conditional on CONFIG_PCI_DOMAINS, but that is now enabled for all PCI
MIPS systems.)

Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Cc: linux-mips@linux-mips.org
Cc: Martin Michlmayr &lt;tbm@cyrius.com&gt;
Cc: Aurelien Jarno &lt;aurelien@aurel32.net&gt;
Cc: 584784@bugs.debian.org
Patchwork: https://patchwork.linux-mips.org/patch/1377/
Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>MIPS: Quit using undefined behavior of ADDU in 64-bit atomic operations.</title>
<updated>2010-09-27T00:21:39Z</updated>
<author>
<name>David Daney</name>
<email>ddaney@caviumnetworks.com</email>
</author>
<published>2010-07-22T18:59:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=74845b58bc3d60d50acd754d3f33fb5a245b7974'/>
<id>urn:sha1:74845b58bc3d60d50acd754d3f33fb5a245b7974</id>
<content type='text'>
commit f2a68272d799bf4092443357142f63b74f7669a1 upstream.

For 64-bit, we must use DADDU and DSUBU.

Signed-off-by: David Daney &lt;ddaney@caviumnetworks.com&gt;
To: linux-mips@linux-mips.org
Patchwork: https://patchwork.linux-mips.org/patch/1483/
Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>AT91: change dma resource index</title>
<updated>2010-09-27T00:21:32Z</updated>
<author>
<name>Nicolas Ferre</name>
<email>nicolas.ferre@atmel.com</email>
</author>
<published>2010-08-20T14:44:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=392cbf6593e72c8fd5ad6c66fb178ede498b83ec'/>
<id>urn:sha1:392cbf6593e72c8fd5ad6c66fb178ede498b83ec</id>
<content type='text'>
commit 8d2602e0778299e2d6084f03086b716d6e7a1e1e upstream.

Reported-by: Dan Liang &lt;dan.liang@atmel.com&gt;
Signed-off-by: Nicolas Ferre &lt;nicolas.ferre@atmel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>IA64: Optimize ticket spinlocks in fsys_rt_sigprocmask</title>
<updated>2010-09-27T00:21:29Z</updated>
<author>
<name>Petr Tesarik</name>
<email>ptesarik@suse.cz</email>
</author>
<published>2010-09-15T22:35:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6e01cc9e2407c3f929c903f5813bc20c079f8e0b'/>
<id>urn:sha1:6e01cc9e2407c3f929c903f5813bc20c079f8e0b</id>
<content type='text'>
commit 2d2b6901649a62977452be85df53eda2412def24 upstream.

Tony's fix (f574c843191728d9407b766a027f779dcd27b272) has a small bug,
it incorrectly uses "r3" as a scratch register in the first of the two
unlock paths ... it is also inefficient.  Optimize the fast path again.

Signed-off-by: Petr Tesarik &lt;ptesarik@suse.cz&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>IA64: fix siglock</title>
<updated>2010-09-27T00:21:29Z</updated>
<author>
<name>Tony Luck</name>
<email>tony.luck@intel.com</email>
</author>
<published>2010-09-09T22:16:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e3c0109cdf6b0656887364b6dd435cb5e7d30b15'/>
<id>urn:sha1:e3c0109cdf6b0656887364b6dd435cb5e7d30b15</id>
<content type='text'>
commit f574c843191728d9407b766a027f779dcd27b272 upstream.

When ia64 converted to using ticket locks, an inline implementation
of trylock/unlock in fsys.S was missed.  This was not noticed because
in most circumstances it simply resulted in using the slow path because
the siglock was apparently not available (under old spinlock rules).

Problems occur when the ticket spinlock has value 0x0 (when first
initialised, or when it wraps around). At this point the fsys.S
code acquires the lock (changing the 0x0 to 0x1. If another process
attempts to get the lock at this point, it will change the value from
0x1 to 0x2 (using new ticket lock rules). Then the fsys.S code will
free the lock using old spinlock rules by writing 0x0 to it. From
here a variety of bad things can happen.

Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>oprofile: Add Support for Intel CPU Family 6 / Model 22 (Intel Celeron 540)</title>
<updated>2010-09-27T00:21:25Z</updated>
<author>
<name>Patrick Simmons</name>
<email>linuxrocks123@netscape.net</email>
</author>
<published>2010-09-08T14:34:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=702c0563a79cb487988dfc83a4e9089435baf8e3'/>
<id>urn:sha1:702c0563a79cb487988dfc83a4e9089435baf8e3</id>
<content type='text'>
commit c33f543d320843e1732534c3931da4bbd18e6c14 upstream.

This patch adds CPU type detection for the Intel Celeron 540, which is
part of the Core 2 family according to Wikipedia; the family and ID pair
is absent from the Volume 3B table referenced in the source code
comments.  I have tested this patch on an Intel Celeron 540 machine
reporting itself as Family 6 Model 22, and OProfile runs on the machine
without issue.

Spec:

 http://download.intel.com/design/mobile/SPECUPDT/317667.pdf

Signed-off-by: Patrick Simmons &lt;linuxrocks123@netscape.net&gt;
Acked-by: Andi Kleen &lt;ak@linux.intel.com&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Robert Richter &lt;robert.richter@amd.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
