Home Home > GIT Browse
diff options
authorRusty Russell <rusty@rustcorp.com.au>2004-02-14 17:31:18 -0800
committerLinus Torvalds <torvalds@home.osdl.org>2004-02-14 17:31:18 -0800
commit103e6e3910db07299355003c59bfb9c05f5c2cf2 (patch)
parent1dfbdec91bee622a25d00aad4511c3f7e5ad18b5 (diff)
[PATCH] Sparc no longer F*cked Up
From: Keith M Wesolowski <wesolows@foobazco.org> As of 2.6.3, restore_flags will no longer modify cwp on sparc. Therefore you can apply this patch to the locking guide. [ Indeed. I'll also remove the atomic comments from Hacking Guide as part of my revision there when I get back to it. --RR ]
1 files changed, 0 insertions, 21 deletions
diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl
index b334f20de271..96d074d97fb6 100644
--- a/Documentation/DocBook/kernel-locking.tmpl
+++ b/Documentation/DocBook/kernel-locking.tmpl
@@ -1444,27 +1444,6 @@ as Alan Cox says, <quote>Lock data, not code</quote>.
- <sect1 id="sparc">
- <title>The Fucked Up Sparc</title>
- <para>
- Alan Cox says <quote>the irq disable/enable is in the register
- window on a sparc</quote>. Andi Kleen says <quote>when you do
- restore_flags in a different function you mess up all the
- register windows</quote>.
- </para>
- <para>
- So never pass the flags word set by
- <function>spin_lock_irqsave()</function> and brethren to another
- function (unless it's declared <type>inline</type>). Usually no-one
- does this, but now you've been warned. Dave Miller can never do
- anything in a straightforward manner (I can say that, because I have
- pictures of him and a certain PowerPC maintainer in a compromising
- position).
- </para>
- </sect1>
<chapter id="Efficiency">