From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] Re: [PATCH v2 4/9] provide in-kernel apic Date: Fri, 09 Oct 2009 14:49:41 -0500 Message-ID: <4ACF93D5.3010002@us.ibm.com> References: <1254953315-5761-1-git-send-email-glommer@redhat.com> <1254953315-5761-2-git-send-email-glommer@redhat.com> <1254953315-5761-3-git-send-email-glommer@redhat.com> <1254953315-5761-4-git-send-email-glommer@redhat.com> <1254953315-5761-5-git-send-email-glommer@redhat.com> <4ACDEF42.6020706@us.ibm.com> <4ACDF297.9010303@redhat.com> <20091008142202.GR8092@mothafucka.localdomain> <20091009100641.GC6576@shareable.org> <20091009143031.GU8092@mothafucka.localdomain> <20091009164831.GB7393@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Glauber Costa , Avi Kivity , qemu-devel@nongnu.org, kvm-devel To: Jamie Lokier Return-path: Received: from e31.co.us.ibm.com ([32.97.110.149]:52405 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752081AbZJITud (ORCPT ); Fri, 9 Oct 2009 15:50:33 -0400 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e31.co.us.ibm.com (8.14.3/8.13.1) with ESMTP id n99JhO2Y019210 for ; Fri, 9 Oct 2009 13:43:24 -0600 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n99JnhFC108770 for ; Fri, 9 Oct 2009 13:49:44 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n99JngXv016270 for ; Fri, 9 Oct 2009 13:49:42 -0600 In-Reply-To: <20091009164831.GB7393@shareable.org> Sender: kvm-owner@vger.kernel.org List-ID: Jamie Lokier wrote: > Glauber Costa wrote: > >> On Fri, Oct 09, 2009 at 11:06:41AM +0100, Jamie Lokier wrote: >> >>> Glauber Costa wrote: >>> >>>>> It ensures the two models are compatible. Since they're the same device >>>>> from the point of view of the guest, there's no reason for them to have >>>>> different representations or to be incompatible. >>>>> >>>> live migration between something that has in-kernel irqchip and >>>> something that has not is likely to be a completely untested >>>> thing. And this is the only reason we might think of it as the same >>>> device. I don't see any value in supporting this combination >>>> >>> Not just live migration. ACPI sleep + savevm + loadvm + ACPI resume, >>> for example. >>> >> Yes, but in this case too, I'd expect the irqchipness of qemu not to change. >> > > If I've just been sent an image produced by someone running KVM, and > my machine is not KVM-capable, or I cannot upgrade the KVM kernel > module because it's in use by other VMs (had this problem a few > times), there's no choice but to change the irqchipness. > You cannot migrate from KVM to TCG so this use-case is irrelevant. -- Regards, Anthony Liguori