On Tue, 2012-06-19 at 23:48 +0200, Alexander Graf wrote: > > We could keep track manually maybe using some kind of dirty bitmap of > > changes to the hash table but that would add overhead to things like > > H_ENTER. > > Only during migration, right?
True. It will be an "interesting" user/kernel API tho ... I'll give it more thoughts. I need to understand better how do that vs. qemu save/restore though. IE. That means we can't just save the hash as a bulk and reload it, but we'd have to save bits of it at a time or something like that no ? Or do we save it once, then save the diff at the end ? Cheers, Ben.
