On 06/14/2011 02:04 PM, Jan Kiszka wrote:
BTW, if Xen is not able to track more than one dirty region, I think it's time to fix that limitation. At some point it may no longer be possible to work around it (who knows how the new memory API will look like in this regard).
Since the memory API eventually passes its decisions to the accelerator (tcg/kvm/xen) it shouldn't be a problem to make the decision there as to which region actually gets logged.
-- error compiling committee.c: too many arguments to function
