From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mt5Ms-0005Dv-JR
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 16:01:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mt5Mp-00059B-25
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 16:01:42 -0400
Received: from [199.232.76.173] (port=57901 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mt5Mo-00058l-ER
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 16:01:38 -0400
Received: from mail-fx0-f214.google.com ([209.85.220.214]:54310)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Mt5Mn-0006Lh-Sb
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 16:01:38 -0400
Received: by fxm10 with SMTP id 10so2146504fxm.8
	for <qemu-devel@nongnu.org>; Wed, 30 Sep 2009 13:01:37 -0700 (PDT)
Message-ID: <4AC3B91C.8000202@codemonkey.ws>
Date: Wed, 30 Sep 2009 15:01:32 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/6] in kernel irqchip support
References: <1254172517-28216-1-git-send-email-glommer@redhat.com>
In-Reply-To: <1254172517-28216-1-git-send-email-glommer@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org

Glauber Costa wrote:
> Hi people,
>
> This (sent with my correct e-mail address) is a port from qemu-kvm.git of
> the in-kernel irqchip support. Right now, I am not providing any way to disable
> it. I am ready to advocate that it should be the default, whenever available.
>
> I plan to, however, provide a patch that disables it whenever this gets merged.
>
> I gave it basic testing, specially with reboot scenarios (due to the load/save)
> functions, and all seems to be working well. But I have only tested linux guests
> so far.
>
> Anthony, I believe it is, although not perfect, in inclusion state.
>   

It breaks the build badly when !CONFIG_IOTHREAD--which is still the default.

Regards,

Anthony Liguori