public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] x86: Use ioremap_cache() for crash dump copies
@ 2009-10-02  3:35 Andi Kleen
  0 siblings, 0 replies; only message in thread
From: Andi Kleen @ 2009-10-02  3:35 UTC (permalink / raw)
  To: x86, linux-kernel; +Cc: venkatesh.pallipadi, stable

During code review I noticed that when reading the previous kernel
memory from a kdump kernel ioremap() is used. This was ok before
the PAT changes, but with PAT ioremap() this results in an uncached
mapping, which is very slow.

Change it to ioremap_cache(). This is fine because this code
only reads real memory, no IO mappings.

I haven't run numbers, but I suspect this will speed up crash dumping
somewhat.

Only affects 64bit, 32bit uses a different method.

Might be a stable candidate.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 arch/x86/kernel/crash_dump_64.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/crash_dump_64.c b/arch/x86/kernel/crash_dump_64.c
index 045b36c..bf43188 100644
--- a/arch/x86/kernel/crash_dump_64.c
+++ b/arch/x86/kernel/crash_dump_64.c
@@ -34,7 +34,7 @@ ssize_t copy_oldmem_page(unsigned long pfn, char *buf,
 	if (!csize)
 		return 0;
 
-	vaddr = ioremap(pfn << PAGE_SHIFT, PAGE_SIZE);
+	vaddr = ioremap_cache(pfn << PAGE_SHIFT, PAGE_SIZE);
 	if (!vaddr)
 		return -ENOMEM;
 
-- 
1.6.0.2


-- 
ak@linux.intel.com -- Speaking for myself only.

^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2009-10-02  3:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-02  3:35 [PATCH] x86: Use ioremap_cache() for crash dump copies Andi Kleen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox