[PATCH v4 05/14] kexec: Add Kexec HandOver (KHO) generation helpers

[Jason Gunthorpe]

On Wed, Feb 12, 2025 at 06:39:06PM +0200, Mike Rapoport wrote:

> As I've mentioned off-list earlier, KHO in its current form is the lowest
> level of abstraction for state preservation and it is by no means is
> intended to provide complex drivers with all the tools necessary.

My point, is I think it is the wrong level of abstraction and the
wrong FDT schema. It does not and cannot solve the problems we know we
will have, so why invest anything into that schema?

I think the scratch system is great, and an amazing improvement over
past version. Upgrade the memory preservation to match and it will be
really good.

> What you propose is a great optimization for memory preservation mechanism,
> and additional and very useful abstraction layer on top of "basic KHO"!

I do not see this as a layer on top, I see it as fundamentally
replacing the memory preservation mechanism with something more
scalable.

> But I think it will be easier to start with something *very simple* and
> probably suboptimal and then extend it rather than to try to build complex
> comprehensive solution from day one.

But why? Just do it right from the start? I spent like a hour
sketching that, the existing preservation code is also very simple,
why not just fix it right now?

Jason