| /openbmc/linux/arch/arm/mm/ |
| H A D | copypage-xsc3.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | proc-syms.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-v4wt.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-feroceon.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-v4wb.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-xscale.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-v4mc.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| H A D | copypage-v6.c | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|
| /openbmc/linux/arch/arm/include/asm/ |
| H A D | page.h | diff 063b0a4207e43acbeff3d4b09f43e750e0212b48 Fri Oct 31 10:08:35 CDT 2008 Russell King <rmk@dyn-67.arm.linux.org.uk> [ARM] copypage: provide our own copy_user_highpage()
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 <rmk+kernel@arm.linux.org.uk>
|