Avi Kivity wrote: > Jan Kiszka wrote: >>> I'm unhappy with both qemu.git and qemu-kvm.git memory slot management; >>> qemu-kvm.git is clumsy, and qemu.git is too simplistic (for example, it >>> ignores the fact that dirty logging is a global resource with multiple >>> users). >>> >> >> Don't get your point yet. Can you name a concrete scenario that is >> problematic in upstream? I'd really like to get slot management right >> there before we drop the old version of qemu-kvm. >> > > If migration disables dirty memory logging, it must keep the vga logging > enabled, and vice versa. So we need some notifier callbacks on slot changes so that all users can re-enable dirty logging after the update as required. Where/how does the migration code disable dirty logging? Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
