On Tue, Aug 15, 2023 at 10:49:12AM +0800, Song Shuai wrote: > > > 在 2023/8/14 19:10, Conor Dooley 写道: > > On Fri, Aug 11, 2023 at 06:41:16PM +0800, Song Shuai wrote: > > > Now we use "memeory::linux,usable-memory" to indicate the available > > > memory for the crash kernel. > > > > > > While booting with UEFI, the crash kernel would use efi.memmap to > > > re-populate memblock and then first kernel's memory would be corrputed. > > > Consequently, the /proc/vmcore file failed to create in my local test. > > > > > > And according to "chosen" dtschema [1], the available memory for the > > > crash kernel should be held via "chosen::linux,usable-memory-range" > > > property which will re-cap memblock even after UEFI's re-population. > > > > > > [1]: > > > https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/chosen.yaml > > > > nit: Please use Link: tags for links rather than free-form text. > > > > This doesn't apply to fixes, for-next or master. What is your base? > > > Actually, I sent these patches to kexec-tools/build-test-riscv-v2, > perhaps I shouldn't cc the linux-riscv mailing list. Oh right, sorry about that!
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
