On 04/09/2015 10:09 PM, Pratyush Anand wrote:
On Thursday 26 March 2015 01:58 PM, AKASHI Takahiro wrote:
Crash dump kernel will access memory regions in system kernel via
copy_oldmem_page(), which reads a page with ioremap'ing it assuming that
such pages are not part of main memory of crash dump kernel.
This is true under non-UEFI environment because kexec-tools modifies
a device tree adding "usablemem" attributes to memory sections.
Under UEFI, however, this is not true because UEFI remove memory
in a device tree and export all the memory regions, even though they
to system kernel.
So we should add "mem=X[MG]" boot parameter to limit the meory size and
avoid hitting the following assertion in ioremap():
Well I am using your updated kexec-tool which has support of automatic
addition of "mem=" parameter. I found that this
warning is still appearing and therefore another error about "Kdump:
vmcore not initialized".
Memory address for which ioremap failed was almost at the top of
crash_reserved_mem. So I modified kexec-tool  to
accept user specific mem= parameter with a value lesser than physical
location which was being remapped, however still
the warning was there.
Further I noticed that there is no reserved memblock with nonzero
memblock_region->size when early_mem ->
memblock_enforce_memory_limit is called. Therefore this mem= param is
not limiting memory location in my case.
On crash dump kernel? Sounds strange.
Can you send me the followings for both 1st kernel and crash dump kernel?
(add memblock_debug to cmd line for verbose messages)
- boot log (dmesg)
- cat /proc/iomem
sending them in a private mail is fine.
I was just wondering, why do not we use ioremap_cache instead of
ioremap in copy_oldmem_page?
My next version of kdump patch uses ioremap_cache() for another reason.
# As I'm discussing with Mark about kvm issue, I'm holding off