From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MwCNJ-00069m-69 for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:07:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MwCNE-00067V-Nz for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:07:00 -0400 Received: from [199.232.76.173] (port=40115 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MwCNE-00067O-6K for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:06:56 -0400 Received: from mail2.shareable.org ([80.68.89.115]:51771) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MwCND-0007QB-KH for qemu-devel@nongnu.org; Fri, 09 Oct 2009 06:06:55 -0400 Date: Fri, 9 Oct 2009 11:06:41 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [PATCH v2 4/9] provide in-kernel apic Message-ID: <20091009100641.GC6576@shareable.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091008142202.GR8092@mothafucka.localdomain> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Glauber Costa Cc: Anthony Liguori , Avi Kivity , kvm-devel , qemu-devel@nongnu.org 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. -- Jamie