[PATCH] unify pfn_to_page take 2 [22/25] sparc64 funcs

[KAMEZAWA Hiroyuki]

Select CONFIG_DONT_INLINE_PFN_TO_PAGE=y
sparc64 can use generic funcs by defining ARCH_PFN_OFFSET as pfn_base.

Signed-Off-By: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxx>


Index: test-layout-free-zone/arch/sparc64/Kconfig
===================================================================
--- test-layout-free-zone.orig/arch/sparc64/Kconfig
+++ test-layout-free-zone/arch/sparc64/Kconfig
@@ -34,6 +34,10 @@ config ARCH_MAY_HAVE_PC_FDC
 	bool
 	default y

+config ARCH_DONT_INLINE_PFN_TO_PAGE
+	bool
+	default y
+
 choice
 	prompt "Kernel page size"
 	default SPARC64_PAGE_SIZE_8KB
Index: test-layout-free-zone/arch/sparc64/mm/init.c
===================================================================
--- test-layout-free-zone.orig/arch/sparc64/mm/init.c
+++ test-layout-free-zone/arch/sparc64/mm/init.c
@@ -320,16 +320,6 @@ void __kprobes flush_icache_range(unsign
 	}
 }

-unsigned long page_to_pfn(struct page *page)
-{
-	return (unsigned long) ((page - mem_map) + pfn_base);
-}
-
-struct page *pfn_to_page(unsigned long pfn)
-{
-	return (mem_map + (pfn - pfn_base));
-}
-
 void show_mem(void)
 {
 	printk("Mem-info:\n");
Index: test-layout-free-zone/include/asm-sparc64/page.h
===================================================================
--- test-layout-free-zone.orig/include/asm-sparc64/page.h
+++ test-layout-free-zone/include/asm-sparc64/page.h
@@ -129,8 +129,7 @@ typedef unsigned long pgprot_t;
  * the first physical page in the machine is at some huge physical address,
  * such as 4GB.   This is common on a partitioned E10000, for example.
  */
-extern struct page *pfn_to_page(unsigned long pfn);
-extern unsigned long page_to_pfn(struct page *);
+#define ARCH_PFN_OFFSET		(pfn_base)

 #define virt_to_page(kaddr)	pfn_to_page(__pa(kaddr)>>PAGE_SHIFT)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/