On Sat, Jan 25, 2025 at 10:19:51AM -0500, Pasha Tatashin wrote: > One way to solve that is pre-reserving space for the KHO tree - > ideally a reasonable amount, perhaps 32-64 MB and allocating it at > kexec load time. Why is there any weird limit? We are preserving hudreds of GB of pages backing the VM and more. There is endless memory being preserved across? So why are we trying to shoehorn a bunch of KHO stuff into the DT? Shouldn't the DT just have a small KHO info pointing to the real KHO memory in normal pages? Even if you want to re-use DT as some kind of serializing scheme in drivers the DT framework can let each driver build its own tree, serialize it to its own memory and then just link a pointer to that tree. Also, I'm not sure forcing using DT as a serializing scheme is a great idea. It is complicated and doesn't do that much to solve the complex versioning problem drivers face here.. Jason
