From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mtq9p-0000sp-Mz for qemu-devel@nongnu.org; Fri, 02 Oct 2009 17:59:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mtq9l-0000jk-Vq for qemu-devel@nongnu.org; Fri, 02 Oct 2009 17:59:21 -0400 Received: from [199.232.76.173] (port=49968 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mtq9l-0000iu-Pi for qemu-devel@nongnu.org; Fri, 02 Oct 2009 17:59:17 -0400 Received: from mail2.shareable.org ([80.68.89.115]:52573) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mtq9k-0006je-En for qemu-devel@nongnu.org; Fri, 02 Oct 2009 17:59:17 -0400 Date: Fri, 2 Oct 2009 22:59:05 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [PATCH 6/6] Initialize in-kernel irqchip Message-ID: <20091002215905.GA2051@shareable.org> References: <1254172517-28216-1-git-send-email-glommer@redhat.com> <1254172517-28216-2-git-send-email-glommer@redhat.com> <1254172517-28216-3-git-send-email-glommer@redhat.com> <1254172517-28216-4-git-send-email-glommer@redhat.com> <1254172517-28216-5-git-send-email-glommer@redhat.com> <1254172517-28216-6-git-send-email-glommer@redhat.com> <1254172517-28216-7-git-send-email-glommer@redhat.com> <4AC663B6.3060705@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AC663B6.3060705@web.de> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Glauber Costa , aliguori@us.ibm.com, qemu-devel@nongnu.org Jan Kiszka wrote: > I agree that in-kernel chips should be default if possible, but I would > keep the possibility to disable them like in qemu-kvm. This helps > specifically to track down issues in their implementations or their > potential side effects. As one of the side effects is to prevent migration to non-KVM hosts (according to an earlier answer), I'd say the option to disable it is essential. Won't that option come for free when we have machine configuration files - by simply specifying one irqchip or the other? -- Jamie