Hi James, > The problem I see with this is rewriting the relocation code. It needs to work whether the > machine has enough memory to enable the MMU during kexec, or not. > > In off-list mail to Pavel I proposed an alternative implementation here: > https://gitlab.arm.com/linux-arm/linux-jm/-/tree/kexec+mmu/v0 > > By using a copy of the linear map, and passing the phys_to_virt offset into > arm64_relocate_new_kernel() its possible to use the same code when we fail to allocate the > page tables, and run with the MMU off as it does today. > I'm convinced someone will crawl out of the woodwork screaming 'regression' if we > substantially increase the amount of memory needed to kexec at all. > > From that discussion: this didn't meet Pavel's timing needs. > If you depend on having all the src/dst pages lined up in a single line, it sounds like > you've over-tuned this to depend on the CPU's streaming mode. What causes the CPU to > start/stop that stuff is very implementation specific (and firmware configurable). > I don't think we should let this rule out systems that can kexec today, but don't have > enough extra memory for the page tables. > Having two copies of the relocation code is obviously a bad idea. I understand that having an extra set of page tables could potentially waste memory, especially if VAs are sparse, but in this case we use page tables exclusively for contiguous VA space (copy [src, src + size]). Therefore, the extra memory usage is tiny. The ratio for kernels with 4K page_size is (size of relocated memory) / 512. A normal initrd + kernel is usually under 64M, an extra space which means ~128K for the page table. Even with a huge relocation, where initrd is ~512M the extra memory usage in the worst case is just ~1M. I really doubt we will have any problem from users because of such small overhead in comparison to the total kexec-load size. > > > (as before: ) Instead of trying to make the relocations run quickly, can we reduce them? > This would benefit other architectures too. This was exactly my first approach [1] where I tried to pre-reserve memory similar to how it is done for a crash kernel, but I was asked to go away [2] as this is an ARM64 specific problem, where current relocation performance is prohibitively slow. I have tested on x86, and it does not suffer from this problem, relocation performance is just as fast as with MMU enabled ARM64. > > Can the kexec core code allocate higher order pages, instead of doing everything page at > at time? Yes, however, failures during kexec-load due to failure to coalesce huge pages can add extra hassle to users, and therefore this should be only an optimization with fallback to base pages. > > If you have a crash kernel reservation, can we use that to eliminate the relocations > completely? > (I think this suggestion has been lost in translation each time I make it. > I mean like this: > https://gitlab.arm.com/linux-arm/linux-jm/-/tree/kexec/kexec_in_crashk/v0 > Runes to test it: > | sudo ./kexec -p -u > | sudo cat /proc/iomem | grep Crash > | b0200000-f01fffff : Crash kernel > | sudo ./kexec --mem-min=0xb0200000 --mem-max=0xf01ffffff -l ~/Image --reuse-cmdline > > I bet its even faster!) There is a problem with this approach. While, with kexec_load() call it is possible to specify physical destinations for each segment, with kexec_file_load() it is not possible. The secure systems that do IMA checks during kexec load require kexec_file_load(), and we cannot ahead of time specify destinations for these segments (at least without substantially changing common kexec code which is not going to happen as this arm64 specific problem). > > > I think 'as fast as possible' and 'memory constrained' are mutually exclusive > requirements. We need to make the page tables optional with a single implementation. In my opinion having two different types of relocations will only add extra corner cases, confusion about different performance, and bugs. It is better to have two types: 1. crash kernel type without relocation, 2. fast relocation where MMU is enabled. [1] https://lore.kernel.org/lkml/20190709182014.16052-1-pasha.tatashin@xxxxxxxxxx [2] https://lore.kernel.org/lkml/20190710065953.GA4744@localhost.localdomain/ Thank you, Pasha
