> I think the UEFI persistent-memory-reservations thing is a better fit for this [0][1]. Hi James, Thank you for your thought. As I understand you propose the to use the existing method as such: 1. Use the existing kexec ABI to pass reservation from kernel to kernel using EFI the same as is done for GICv3 tables. 2. Allow this memory to be reservable only during first Linux boot via EFI memory reserve 3. Allow to have this memory pre-reserved by firmware or to be embedded into device tree. A question I have is how to tell that a reserved region is reserved for IMA use. With GICv3 it is done by reading the registers, finding the interrupt tables memory, and check that the memory ranges are indeed pre-reserved. Is there a way to name memory with the current ABI that you think is acceptable? Thank you, Pasha
