From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxME0-0003aD-Ue for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxMDt-0003RL-NW for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:10 -0400 Received: from [199.232.76.173] (port=39730 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxMDt-0003Qu-Ei for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:05 -0400 Received: from fg-out-1718.google.com ([72.14.220.156]:54175) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxMDq-00026B-VG for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:03 -0400 Received: by fg-out-1718.google.com with SMTP id d23so2475888fga.10 for ; Mon, 12 Oct 2009 07:50:01 -0700 (PDT) Message-ID: <4AD34212.9060805@codemonkey.ws> Date: Mon, 12 Oct 2009 09:49:54 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1254953315-5761-4-git-send-email-glommer@redhat.com> <4ACDEDEC.60706@us.ibm.com> <4ACDEF03.6010406@redhat.com> <20091008160726.GD29691@shareable.org> <4ACE10B5.3080509@redhat.com> <20091008162248.GK16702@redhat.com> <20091009143225.GV8092@mothafucka.localdomain> <20091009164955.GC7393@shareable.org> <4AD32D22.5090001@us.ibm.com> <20091012141825.GC13560@shareable.org> In-Reply-To: <20091012141825.GC13560@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH v2 3/9] provide in-kernel ioapic List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Anthony Liguori , kvm-devel , Gleb Natapov , Glauber Costa , qemu-devel@nongnu.org, Juan Quintela , Avi Kivity Jamie Lokier wrote: > Anthony Liguori wrote: > >> We already have the single device model implementation and the >> limitations are well known. The best way to move forward is for someone >> to send out patches implementing separate device models. >> >> At that point, it becomes a discussion of two concrete pieces of code >> verses hand waving. >> > > Out of curiosity now, what _are_ the behavioural differences between > the in-kernel irqchip and the qemu one? > > Are the differences significant to guests, such that it might be > necessary to disable the in-kernel irqchip for some guests, or > conversely, necessary to use KVM for some guests? > No, the behavior differences are not terribly significant for the apic. Disabling it is really most useful for debugging purposes. Regards, Anthony Liguori