Re: [PATCH -v2 06/13] x86, mm: Separate out calculate_table_space_size()

2012-09-02 Thread Pekka Enberg
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu wrote: > it should take physical address range that will need to be mapped. > and find_early_table_space should take range that pgt buff should be in. > Separate those two to reduce confusion. > > Signed-off-by: Yinghai Lu Reviewed-by: Pekka Enberg

[PATCH -v2 06/13] x86, mm: Separate out calculate_table_space_size()

2012-09-02 Thread Yinghai Lu
it should take physical address range that will need to be mapped. and find_early_table_space should take range that pgt buff should be in. Separate those two to reduce confusion. Signed-off-by: Yinghai Lu --- arch/x86/mm/init.c | 39 --- 1 files changed,

[PATCH -v2 06/13] x86, mm: Separate out calculate_table_space_size()

2012-09-02 Thread Yinghai Lu
it should take physical address range that will need to be mapped. and find_early_table_space should take range that pgt buff should be in. Separate those two to reduce confusion. Signed-off-by: Yinghai Lu ying...@kernel.org --- arch/x86/mm/init.c | 39 ---

Re: [PATCH -v2 06/13] x86, mm: Separate out calculate_table_space_size()

2012-09-02 Thread Pekka Enberg
On Sun, Sep 2, 2012 at 10:46 AM, Yinghai Lu ying...@kernel.org wrote: it should take physical address range that will need to be mapped. and find_early_table_space should take range that pgt buff should be in. Separate those two to reduce confusion. Signed-off-by: Yinghai Lu