From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: Re: [PATCH v2 4/9] provide in-kernel apic Date: Fri, 9 Oct 2009 11:06:41 +0100 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 Cc: Anthony Liguori , Avi Kivity , kvm-devel , qemu-devel@nongnu.org To: Glauber Costa Return-path: Content-Disposition: inline In-Reply-To: <20091008142202.GR8092@mothafucka.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.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