On 27/11/20 11:58, Alexander Graf wrote:
Mostly because there is a lot of super fragile logic all over resets
atm. Init setts dirty, post-init clears it. Then the arch reset handlers
assume that state is not dirty and fiddle with KVM reset ioctls and KVM
register modification ioctls directly. Mostly because KVM for the most
part implements its own reset logic.
I'm fairy sure I'd break someone unintentionally if I just throw this
into the common reset handler.
However, if we're happy to fix the fallout when it arises, I'm happy to
do so.
I'll decline the offer. ;)
Paolo
