From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtqWa-00023I-TT for qemu-devel@nongnu.org; Fri, 02 Oct 2009 18:22:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtqWW-000206-4j for qemu-devel@nongnu.org; Fri, 02 Oct 2009 18:22:52 -0400 Received: from [199.232.76.173] (port=42847 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtqWV-000202-V9 for qemu-devel@nongnu.org; Fri, 02 Oct 2009 18:22:47 -0400 Received: from mail-yx0-f173.google.com ([209.85.210.173]:64172) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtqWV-0001uD-Kt for qemu-devel@nongnu.org; Fri, 02 Oct 2009 18:22:47 -0400 Received: by yxe3 with SMTP id 3so1461340yxe.4 for ; Fri, 02 Oct 2009 15:22:45 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <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> <20091002215905.GA2051@shareable.org> Date: Fri, 2 Oct 2009 19:22:44 -0300 Message-ID: <5d6222a80910021522s3b623529i6f3ef60d97875362@mail.gmail.com> Subject: Re: [Qemu-devel] Re: [PATCH 6/6] Initialize in-kernel irqchip From: Glauber Costa Content-Type: text/plain; charset=UTF-8 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Glauber Costa , Jan Kiszka , aliguori@us.ibm.com, qemu-devel@nongnu.org On Fri, Oct 2, 2009 at 6:59 PM, Jamie Lokier wrote: > 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? Even if it does, I have code for that already. I will post when I repost that series. > -- Jamie > > > -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act."