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 --pass-memmap option. And also in new kernel we > > need to retain saved_max_pfn. Only difference will be, that we will > > set saved_max_pfn only if it is kdump kernel and if user passed a > > memory map on kernel command line. > > Old first kernel and new second kernel is easy to handle. Like you said, > we can use exactmap and set saved_max_pfn in kdump kernel, just as the > old way. > > But it's still not clear to me how we can handle the case of new first > kernel and old second kernel. > > Let's say, a calgary system has 2G memory. The new first kernel TCE > table size are hard coded to 8M. When the old kdump kernel is booting, > memmap=exactmap is parsed and saved_max_pfn is set to 2G/PAGE_SIZE. TCE > table size is determined by 2G ram size. So the size is 4M. We run into > the situation that TCE table is 8M in first kernel and 4M in second > kernel. This inconsistency of TCE table size would cause kdump kernel > fails somehow, that's why we brought in saved_max_pfn in the first place > as you know. > > The problem is how to keep TCE table size being consistent between new > first kernel and old second kernel. You are right. I did not think through it. So we can't handle the case of new first kernel and second old kernel without exporting size of tables to user space. Given the fact that calgary is old hardware, exporting table size to user space is not very prudent. I would say let us handle the case of old first kernel and second new kernel to maintain backward compatibility. Thanks Vivek
