05 Oct, 2009
1 commit
-
Our copy_user_highpage() implementations may require cache maintainence.
Ensure that implementations have all necessary details to perform this
maintainence.Signed-off-by: Russell King
13 Mar, 2009
1 commit
-
This is a fix for the following crash observed in 2.6.29-rc3:
http://lkml.org/lkml/2009/1/29/150On ARM it doesn't make sense to trace a naked function because then
mcount is called without stack and frame pointer being set up and there
is no chance to restore the lr register to the value before mcount was
called.Reported-by: Matthias Kaehlcke
Tested-by: Matthias KaehlckeCc: Abhishek Sagar
Cc: Steven Rostedt
Cc: Ingo Molnar
Signed-off-by: Uwe Kleine-König
Signed-off-by: Russell King
28 Nov, 2008
4 commits
-
In all cases the kaddr is assigned an input register even though it is
modified in the assembly code. Let's assign a new variable to the
modified value and mark those inline asm with volatile otherwise they
get optimized away because the output variable is otherwise not used.Also fix a few conversion errors in copypage-feroceon.c and
copypage-v4mc.c.Signed-off-by: Nicolas Pitre
Signed-off-by: Russell King -
For similar reasons as copy_user_page(), we want to avoid the
additional kmap_atomic if it's unnecessary.Signed-off-by: Russell King
-
We used to override the copy_user_page() function. However, this
is not only inefficient, it also causes additional complexity for
highmem support, since we convert from a struct page to a kernel
direct mapped address and back to a struct page again.Moreover, with highmem support, we end up pointlessly setting up
kmap entries for pages which we're going to remap. So, push the
kmapping down into the copypage implementation files where it's
required.Signed-off-by: Russell King
-
Signed-off-by: Russell King
