kumi

Configuration UI can be added regardless of what happens with defaults. Defaults change is not a blocker for exposing configurability. If anything I'd say you got it backwards: Don't switch long-standing defaults until there is a discoverable and accessible way to change it.

Thank you, I'm glad you like!

not having worked with memmap before, it is not immediately obvious to me which hex means what (I am guessing RANGE@START? ). Would be nice to have a link to an explanation there.

I just have the link to the kernel docs because I think they do a better job explaining it than I would 😁

But yeah, basically. Except for this use-case you want RANGE$START not @. And you can use human sizes like 128M$RANGE.

There is one part in the post mentioning how to "pad holes" in failing areas. Maybe I should expand it with some details around aligning reserved address space.

Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.