<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/arch, branch v2.6.24.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/arch?h=v2.6.24.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/arch?h=v2.6.24.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2008-03-24T18:48:36Z</updated>
<entry>
<title>S390 futex: let futex_atomic_cmpxchg_pt survive early functional tests.</title>
<updated>2008-03-24T18:48:36Z</updated>
<author>
<name>Heiko Carstens</name>
<email>heiko.carstens@de.ibm.com</email>
</author>
<published>2008-03-20T16:33:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=78d05881017eef1e9ea49571c52275dc2935e719'/>
<id>urn:sha1:78d05881017eef1e9ea49571c52275dc2935e719</id>
<content type='text'>
a0c1e9073ef7428a14309cba010633a6cd6719ea "futex: runtime enable pi and
robust functionality" introduces a test wether futex in atomic stuff
works or not.
It does that by writing to address 0 of the kernel address space. This
will crash on older machines where addressing mode switching is enabled
but where the mvcos instruction is not available. Page table walking is
done by hand and therefore the code tries to access current-&gt;mm which
is NULL.
Therefore add an extra check, so we survive the early test.

Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;
Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;
Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>x86: move out tick_nohz_stop_sched_tick() call from the loop</title>
<updated>2008-03-24T18:47:32Z</updated>
<author>
<name>Hiroshi Shimamoto</name>
<email>h-shimamoto@ct.jp.nec.com</email>
</author>
<published>2008-01-30T12:33:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a542b46db3536a4009b618609058a44edad9d22d'/>
<id>urn:sha1:a542b46db3536a4009b618609058a44edad9d22d</id>
<content type='text'>
[upstream commit: 3d97775a]

Move out tick_nohz_stop_sched_tick() call from the loop in cpu_idle
same as 32-bit version.

Signed-off-by: Hiroshi Shimamoto &lt;h-shimamoto@ct.jp.nec.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Cc: Ed Tomlinson &lt;edt@aei.ca&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>PCI x86: always use conf1 to access config space below 256 bytes</title>
<updated>2008-03-24T18:47:27Z</updated>
<author>
<name>Ivan Kokshaysky</name>
<email>ink@jurassic.park.msu.ru</email>
</author>
<published>2008-01-14T22:31:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b39bf4a535df7afb304cc3884b669210036cb960'/>
<id>urn:sha1:b39bf4a535df7afb304cc3884b669210036cb960</id>
<content type='text'>
[upsteam commit: a0ca9909]

Thanks to Loic Prylli &lt;loic@myri.com&gt;, who originally proposed
this idea.

Always using legacy configuration mechanism for the legacy config space
and extended mechanism (mmconf) for the extended config space is
a simple and very logical approach. It's supposed to resolve all
known mmconf problems. It still allows per-device quirks (tweaking
dev-&gt;cfg_size). It also allows to get rid of mmconf fallback code.

This patch fixes a boot hang on Intel Q35 chipset as detailed at:
  http://bugs.gentoo.org/198810

Signed-off-by: Ivan Kokshaysky &lt;ink@jurassic.park.msu.ru&gt;
Signed-off-by: Matthew Wilcox &lt;willy@linux.intel.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Mike Pagano &lt;mpagano@gentoo.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>ARM pxa: fix clock lookup to find specific device clocks</title>
<updated>2008-03-24T18:47:17Z</updated>
<author>
<name>Russell King</name>
<email>rmk+kernel@arm.linux.org.uk</email>
</author>
<published>2008-02-24T14:55:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e08b12e87e90a96df9380e8b17424e939c9f3448'/>
<id>urn:sha1:e08b12e87e90a96df9380e8b17424e939c9f3448</id>
<content type='text'>
commit: a0dd005d1d9f4c3beab52086f3844ef9342d1e67

Ensure that the clock lookup always finds an entry for a specific
device and ID before it falls back to finding just by ID.  This
fixes a problem reported by Holger Schurig where the BTUART was
assigned the wrong clock.

Tested-by: Holger Schurig &lt;hs4233@mail.mn-solutions.de&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;

Uli Luckas notes:

  The patch fixes the otherwise unusable bluetooth uart on pxa25x. The
  patch is written by Russell King [1] who also gave his OK for
  stable inclusion [2].  The patch is also available as commit
  a0dd005d1d9f4c3beab52086f3844ef9342d1e67 to Linus' tree.

  [1] http://marc.info/?l=linux-arm-kernel&amp;m=120298366510315
  [2] http://marc.info/?l=linux-arm-kernel&amp;m=120384388411097

Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>x86: adjust enable_NMI_through_LVT0()</title>
<updated>2008-03-24T18:47:11Z</updated>
<author>
<name>Jan Beulich</name>
<email>jbeulich@novell.com</email>
</author>
<published>2008-03-11T10:30:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=41abba651b51394ae1119ac26bd1dd2e31bc2dc0'/>
<id>urn:sha1:41abba651b51394ae1119ac26bd1dd2e31bc2dc0</id>
<content type='text'>
commit e94271017f0933b29362a3c9dea5a6b9d04d98e1

Its previous use in a call to on_each_cpu() was pointless, as at the
time that code gets executed only one CPU is online. Further, the
function can be __cpuinit, and for this to work without
CONFIG_HOTPLUG_CPU setup_nmi() must also get an attribute (this one
can even be __init; on 64-bits check_timer() also was lacking that
attribute).

Signed-off-by: Jan Beulich &lt;jbeulich@novell.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
[ tglx@linutronix.de: backport to 2.6.24.3]
Cc: Justin Piszcz &lt;jpiszcz@lucidpixels.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>x86: Clear DF before calling signal handler</title>
<updated>2008-03-24T18:47:10Z</updated>
<author>
<name>Aurelien Jarno</name>
<email>aurelien@aurel32.net</email>
</author>
<published>2008-03-08T10:43:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cc7571b226c93b032164ebb3ff3b365651c4652f'/>
<id>urn:sha1:cc7571b226c93b032164ebb3ff3b365651c4652f</id>
<content type='text'>
x86: Clear DF before calling signal handler

The Linux kernel currently does not clear the direction flag before
calling a signal handler, whereas the x86/x86-64 ABI requires that.
This become a real problem with gcc version 4.3, which assumes that
the direction flag is correctly cleared at the entry of a function.

This patches changes the setup_frame() functions to clear the
direction before entering the signal handler.

This is a backport of patch e40cd10ccff3d9fbffd57b93780bee4b7b9bff51
("x86: clear DF before calling signal handler") that has been applied
in 2.6.25-rc.

Signed-off-by: Aurelien Jarno &lt;aurelien@aurel32.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>MIPS: Mark all but i8259 interrupts as no-probe.</title>
<updated>2008-03-24T18:47:09Z</updated>
<author>
<name>Ralf Baechle</name>
<email>ralf@linux-mips.org</email>
</author>
<published>2008-02-08T12:22:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a1843b4dedab81c769ccdce4ec9ed2fce6f6ad90'/>
<id>urn:sha1:a1843b4dedab81c769ccdce4ec9ed2fce6f6ad90</id>
<content type='text'>
Use set_irq_noprobe() to mark all MIPS interrupts as non-probe.  Override that
default for i8259 interrupts.

Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Acked-and-tested-by: Rob Landley &lt;rob@landley.net&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: Ingo Molnar &lt;mingo@elte.hu&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>SPARC: Fix link errors with gcc-4.3</title>
<updated>2008-03-24T18:47:04Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2008-03-06T22:47:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7564c2eb8926cc19fe06f8b0c6f9f08628c544da'/>
<id>urn:sha1:7564c2eb8926cc19fe06f8b0c6f9f08628c544da</id>
<content type='text'>
Upstream commit: f0e98c387e61de00646be31fab4c2fa0224e1efb

Reported by Adrian Bunk.

Just like in changeset a3f9985843b674cbcb58f39fab8416675e7ab842
("[SPARC64]: Move kernel unaligned trap handlers into assembler
file.") we have to move the assembler bits into a seperate
asm file because as far as the compiler is concerned
these inline bits we're doing in unaligned.c are unreachable.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>SPARC64: Loosen checks in exception table handling.</title>
<updated>2008-03-24T18:47:03Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2008-03-06T22:47:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=68b498d251d97de9adda518fda42cfe1451063b7'/>
<id>urn:sha1:68b498d251d97de9adda518fda42cfe1451063b7</id>
<content type='text'>
Upstream commits: 622eaec613130e6ea78f2a5d5070e3278b21cd8f
                  be71716e464f4ea38f08034dc666f2feb55535d9

Some parts of the kernel now do things like do *_user() accesses while
set_fs(KERNEL_DS) that fault on purpose.

See, for example, the code added by changeset
a0c1e9073ef7428a14309cba010633a6cd6719ea ("futex: runtime enable pi
and robust functionality").

That trips up the ASI sanity checking we make in do_kernel_fault().

Just remove it for now.  Maybe we can add it back later with an added
conditional which looks at the current get_fs() value.

Also, because of the new futex validation init handler, we have
to accept faults in init section text as well as the normal
kernel text.

Thanks to Tom Callaway for the bug report.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>x86_64: CPA, fix cache attribute inconsistency bug</title>
<updated>2008-02-26T00:19:02Z</updated>
<author>
<name>Ingo Molnar</name>
<email>mingo@elte.hu</email>
</author>
<published>2008-02-15T19:59:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7a0fd2e6b0190e5dd2bfe71a0b4f10826811418e'/>
<id>urn:sha1:7a0fd2e6b0190e5dd2bfe71a0b4f10826811418e</id>
<content type='text'>
(no matching git id as the upstream code is rewritten)

fix CPA cache attribute bug in v2.6.24. When phys_base is nonzero (when 
CONFIG_RELOCATABLE=y) then change_page_attr_addr() miscalculates the 
secondary alias address by -14 MB (depending on the configured offset).

The default 64-bit kernels of Fedora and Ubuntu are affected:

   $ grep RELOCA /boot/config-2.6.23.9-85.fc8
     CONFIG_RELOCATABLE=y

   $ grep RELOC /boot/config-2.6.22-14-generic
     CONFIG_RELOCATABLE=y

and probably on many other distros as well.

the bug affects all pages in the first 40 MB of physical RAM that
are allocated by some subsystem that does ioremap_nocache() on them:

       if (__pa(address) &lt; KERNEL_TEXT_SIZE) {

Hence we might leave page table entries with inconsistent cache
attributes around (pages mapped at both UnCacheable and Write-Back),
and we can also set the wrong kernel text pages to UnCacheable.

the effects of this bug can be random slowdowns and other misbehavior.
If for example AGP allocates its aperture pages into the first 40 MB
of physical RAM, then the -14 MB bug might mark random kernel texto
pages as uncacheable, slowing down a random portion of the 64-bit
kernel until the AGP driver is unloaded.

Signed-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;
Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

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