From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Date: Wed, 29 Apr 2009 11:12:48 +0000 Subject: Re: qemu-kvm.git now live Message-Id: <49F83630.6020402@redhat.com> List-Id: References: <49F08BD0.6000706@redhat.com> In-Reply-To: <49F08BD0.6000706@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ia64@vger.kernel.org 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. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Date: Wed, 29 Apr 2009 11:12:48 +0000 Subject: Re: qemu-kvm.git now live Message-Id: <49F83630.6020402@redhat.com> List-Id: References: <49F08BD0.6000706@redhat.com> <49F81496.8030407@siemens.com> <49F82F24.8040506@redhat.com> <49F83227.9000502@siemens.com> In-Reply-To: <49F83227.9000502-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jan Kiszka Cc: KVM list , Anthony Liguori , Hollis Blanchard , "Zhang, Xiantao" , kvm-ppc , "kvm-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Carsten Otte 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. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu-kvm.git now live Date: Wed, 29 Apr 2009 14:12:48 +0300 Message-ID: <49F83630.6020402@redhat.com> References: <49F08BD0.6000706@redhat.com> <49F81496.8030407@siemens.com> <49F82F24.8040506@redhat.com> <49F83227.9000502@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list , Anthony Liguori , Hollis Blanchard , "Zhang, Xiantao" , kvm-ppc , "kvm-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Carsten Otte To: Jan Kiszka Return-path: In-Reply-To: <49F83227.9000502-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org> Sender: kvm-ppc-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: kvm.vger.kernel.org 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. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html