Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-10 Thread Vivek Goyal
On Mon, Mar 10, 2014 at 04:38:34PM +0800, WANG Chao wrote: [..] > > So we have two scenarios. > > > > - Old first kernel and new second kernel. > > - New first kernel and old second kernel. > > > > If we want to make these two scenarios work with calgary, we need to > > use kexec-tools with --pa

Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-10 Thread WANG Chao
On 03/07/14 at 11:09am, Vivek Goyal wrote: > On Fri, Mar 07, 2014 at 11:52:04PM +0800, WANG Chao wrote: > > Hi, Vivek > > > > On 03/07/14 at 09:14am, Vivek Goyal wrote: > > > On Fri, Mar 07, 2014 at 04:10:16PM +0800, WANG Chao wrote: > > > > > > [..] > > > > } > > > > > > > > - sp

Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-08 Thread Muli Ben-Yehuda
On Fri, Mar 07, 2014 at 11:09:06AM -0500, Vivek Goyal wrote: > I would say it is not very complicated to maintain backward > compatibility in this case. So let us keep saved_max_pfn for some > time and make kexec-tools changes. Some time down the line, one can > get rid of saved_max_pfn completely

Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-07 Thread Vivek Goyal
On Fri, Mar 07, 2014 at 11:52:04PM +0800, WANG Chao wrote: > Hi, Vivek > > On 03/07/14 at 09:14am, Vivek Goyal wrote: > > On Fri, Mar 07, 2014 at 04:10:16PM +0800, WANG Chao wrote: > > > > [..] > > > } > > > > > > - specified_table_size = determine_tce_table_size((is_kdump_kernel() ? > > > -

Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-07 Thread WANG Chao
Hi, Vivek On 03/07/14 at 09:14am, Vivek Goyal wrote: > On Fri, Mar 07, 2014 at 04:10:16PM +0800, WANG Chao wrote: > > [..] > > } > > > > - specified_table_size = determine_tce_table_size((is_kdump_kernel() ? > > - saved_max_pfn : max_pfn) * PAGE_SIZE); >

Re: [PATCH] x86, calgary: use 8M TCE table size by default

2014-03-07 Thread Vivek Goyal
On Fri, Mar 07, 2014 at 04:10:16PM +0800, WANG Chao wrote: [..] > } > > - specified_table_size = determine_tce_table_size((is_kdump_kernel() ? > - saved_max_pfn : max_pfn) * PAGE_SIZE); > + specified_table_size = determine_tce_table_size(); I do

[PATCH] x86, calgary: use 8M TCE table size by default

2014-03-07 Thread WANG Chao
kexec-tools wants to pass kdump kernel needed memmap via E820 directly, instead of memmap=exactmap. That'll make saved_max_pfn totally useless. Muli suggest to hard code TCE table size to max (8M) so that kdump kernel could use this default size and kexec-tools doesn't need to pass saved_max_pfn t