From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGB4L-0000QJ-Tw
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 07:46:02 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGB4H-0000Nh-3P
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 07:46:01 -0500
Received: from [199.232.76.173] (port=48419 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGB4G-0000NK-2h
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 07:45:56 -0500
Received: from mx1.redhat.com ([209.132.183.28]:41322)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NGB4F-0001pB-JS
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 07:45:55 -0500
Message-ID: <4B17B300.4070803@redhat.com>
Date: Thu, 03 Dec 2009 14:45:52 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 0/9] in-kernel irqchip, new spin
References: <1259761575-3953-1-git-send-email-glommer@redhat.com>
	<20091203102701.GC6752@redhat.com>
	<5d6222a80912030342m499eb913lff5fc7a21b142718@mail.gmail.com>
	<20091203115729.GC7352@redhat.com>
	<5d6222a80912030404m2cc09946wf3391f10227efcee@mail.gmail.com>
	<20091203123924.GF7352@redhat.com>
In-Reply-To: <20091203123924.GF7352@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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Glauber Costa <glommer@gmail.com>, Glauber Costa <glommer@redhat.com>, aliguori@us.ibm.com, qemu-devel@nongnu.org

On 12/03/2009 02:39 PM, Michael S. Tsirkin wrote:
>>
>> Right now there are no knobs to disable it, since last time I checked,
>> people were inclined to
>> solve that by adding a machine type that does not do irqchip in
>> kernel, if wanted.
>>      
> Can't everything doable by machine type also doable from
> command line switch? Disabling irqchip used to be
> a valuable debugging tool.
>
>    

Even worse, if we throw everything into the the machine type, we end up 
with 2^n machine types in order to control everything.

-- 
error compiling committee.c: too many arguments to function