Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap

2006-12-08 Thread KAMEZAWA Hiroyuki
This removes implicit default actions in map_generic_kernel() call. Also changes comments in vmalloc.h Signed-Off-By: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> Index: devel-2.6.19/include/linux/vmalloc.h === --- devel-2.6.19.orig/include

Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap

2006-12-08 Thread KAMEZAWA Hiroyuki
On Fri, 8 Dec 2006 16:28:19 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote: > Generally we prefer to simply *require* that the function vector be filled > in appropriately. So if the caller has no special needs, the caller will > set their gen_map_kern_ops.k_pte_alloc to point at pte_alloc_kernel(

Re: [RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap

2006-12-08 Thread Andrew Morton
On Fri, 8 Dec 2006 16:01:42 +0900 KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote: > When we want to map pages into the kernel space by vmalloc()'s routine, > we always need 'struct page' to do that. > > There are cases where there is no page struct to use (bootstrap, etc..). > This function is desig

[RFC] [PATCH] virtual memmap on sparsemem v3 [1/4] map and unmap

2006-12-07 Thread KAMEZAWA Hiroyuki
When we want to map pages into the kernel space by vmalloc()'s routine, we always need 'struct page' to do that. There are cases where there is no page struct to use (bootstrap, etc..). This function is designed to help map any memory to anywhere, anytime. Users should manage their virtual/physic