On Wed, 2012-06-20 at 00:27 +0200, Alexander Graf wrote: > > > 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 ? > > The best way would be to throw it into the same bucket as RAM. At the > end of the day, it really is no different. It'd then be synced during > every iteration of the migration.
Sure, I understand the principle on paper :-) Not the details on how to do that in the code :-) I'll dig see if I can figure it out from the RAM code later this week. I'm not actually implementing that stuff just yet, just sizing it. Cheers, Ben.
