<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/sh/mm, branch linux-3.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-10-09T07:22:47Z</updated>
<entry>
<title>readahead: fault retry breaks mmap file read random detection</title>
<updated>2012-10-09T07:22:47Z</updated>
<author>
<name>Shaohua Li</name>
</author>
<published>2012-10-08T23:32:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=45cac65b0fcd287ebb877b141d40ba9bbe8e5da7'/>
<id>urn:sha1:45cac65b0fcd287ebb877b141d40ba9bbe8e5da7</id>
<content type='text'>
.fault now can retry.  The retry can break state machine of .fault.  In
filemap_fault, if page is miss, ra-&gt;mmap_miss is increased.  In the second
try, since the page is in page cache now, ra-&gt;mmap_miss is decreased.  And
these are done in one fault, so we can't detect random mmap file access.

Add a new flag to indicate .fault is tried once.  In the second try, skip
ra-&gt;mmap_miss decreasing.  The filemap_fault state machine is ok with it.

I only tested x86, didn't test other archs, but looks the change for other
archs is obvious, but who knows :)

Signed-off-by: Shaohua Li &lt;shaohua.li@fusionio.com&gt;
Cc: Rik van Riel &lt;riel@redhat.com&gt;
Cc: Wu Fengguang &lt;fengguang.wu@intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix up recursive fault in oops with unset TTB.</title>
<updated>2012-07-25T04:11:13Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-07-24T04:15:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=90eed7d87b748f9c0d11b9bad64a4c41e31b78c4'/>
<id>urn:sha1:90eed7d87b748f9c0d11b9bad64a4c41e31b78c4</id>
<content type='text'>
Presently the oops code looks for the pgd either from the mm context or
the cached TTB value. There are presently cases where the TTB can be
unset or otherwise cleared by hardware, which we weren't handling,
resulting in recursive faults on the NULL pgd. In these cases we can
simply reload from swapper_pg_dir and continue on as normal.

Cc: stable@vger.kernel.org
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Fix up section mismatch warnings.</title>
<updated>2012-06-14T06:05:53Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-06-14T06:05:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0412ddc82223ea2bb3a9db21355e5fe0862a97e5'/>
<id>urn:sha1:0412ddc82223ea2bb3a9db21355e5fe0862a97e5</id>
<content type='text'>
WARNING: vmlinux.o(.cpuinit.text+0x280): Section mismatch in reference from the function cpu_probe() to the function .init.text:sh64_tlb_init()
The function __cpuinit cpu_probe() references
a function __init sh64_tlb_init().
If sh64_tlb_init is only used by cpu_probe then
annotate sh64_tlb_init with a matching annotation.

sh64_tlb_init() simply needs to be __cpuinit annotated, so fix that up.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Fix up vmalloc fault range check.</title>
<updated>2012-05-18T11:01:16Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-18T11:01:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d8fd35fc586f74b2defe011d3a2bfb507871a407'/>
<id>urn:sha1:d8fd35fc586f74b2defe011d3a2bfb507871a407</id>
<content type='text'>
With the previous attempt reverted this switches to conditionalizing the
end address. Nominally VMALLOC_END, but extended for P3_ADDR_MAX in the
store queue case.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>Revert "sh: Ensure fixmap and store queue space can co-exist."</title>
<updated>2012-05-18T10:30:05Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-18T10:30:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c3e0af98792f9f1c840dc969f883e46d0ced3e00'/>
<id>urn:sha1:c3e0af98792f9f1c840dc969f883e46d0ced3e00</id>
<content type='text'>
This reverts commit 20e7c297efeca0861adcca073a0d283da659834b.
With store queues enabled the area above P4SEG has special properties
from the MMU's point of view, which was causing fixmap failure. We'll
have to do something else to satisfy the vmalloc range check.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Set additional fault code values.</title>
<updated>2012-05-14T08:46:49Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-14T08:46:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fd37e75ed56e3f9ddde15c57a9cbde8256221404'/>
<id>urn:sha1:fd37e75ed56e3f9ddde15c57a9cbde8256221404</id>
<content type='text'>
The SSR.MD status amongst other things are already made available, which
can be used for encoding a more precise fault code value.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Tidy up and consolidate the TLB miss fast path.</title>
<updated>2012-05-14T08:24:21Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-14T08:24:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=392c3822a6fc247c0708c9e52c0818d1fbc9d7d7'/>
<id>urn:sha1:392c3822a6fc247c0708c9e52c0818d1fbc9d7d7</id>
<content type='text'>
This unifies the fast-path TLB miss handler, allowing for further cleanup
and eventual utilization of a shared _32/_64 handler.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Fix up caller-save register settings for fast-path.</title>
<updated>2012-05-14T07:46:07Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-14T07:46:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2ec08e141f88328e8a4d24590e9a2406633a0898'/>
<id>urn:sha1:2ec08e141f88328e8a4d24590e9a2406633a0898</id>
<content type='text'>
Now that the fast-path handler has been moved, we also need to update the
Makefile to ensure that the same restrictions for caller-save registers
are observed.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Invert page fault fast-path error path values.</title>
<updated>2012-05-14T07:44:45Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-14T07:44:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4de5185629f44942f60e2fd536709ef31bd5a9c1'/>
<id>urn:sha1:4de5185629f44942f60e2fd536709ef31bd5a9c1</id>
<content type='text'>
This brings the sh64 version in line with the sh32 one with regards to
how errors are handled. Base work for further unification of the
implementations.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh64: Migrate to __update_tlb() API.</title>
<updated>2012-05-14T06:52:28Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2012-05-14T06:52:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c06fd28387a3da2cc4763f7f471f735ccdd61b88'/>
<id>urn:sha1:c06fd28387a3da2cc4763f7f471f735ccdd61b88</id>
<content type='text'>
Now that we have a method for finding out if we're handling an ITLB fault
or not without passing it all the way down the chain, it's possible to
use the __update_tlb() interface in place of a special __do_tlb_refill().

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