From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:38584)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aliguori@us.ibm.com>) id 1RpiPU-0003OJ-Jj
	for qemu-devel@nongnu.org; Tue, 24 Jan 2012 10:35:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aliguori@us.ibm.com>) id 1RpiPO-0001xA-MD
	for qemu-devel@nongnu.org; Tue, 24 Jan 2012 10:35:48 -0500
Received: from e38.co.us.ibm.com ([32.97.110.159]:37757)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aliguori@us.ibm.com>) id 1RpiPO-0001wq-Dw
	for qemu-devel@nongnu.org; Tue, 24 Jan 2012 10:35:42 -0500
Received: from /spool/local
	by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only!
	Violators will be prosecuted
	for <qemu-devel@nongnu.org> from <aliguori@us.ibm.com>;
	Tue, 24 Jan 2012 08:35:40 -0700
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com
	[9.17.195.226])
	by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 19B2E1FF005A
	for <qemu-devel@nongnu.org>; Tue, 24 Jan 2012 08:34:53 -0700 (MST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id
	q0OFYf1Y139936
	for <qemu-devel@nongnu.org>; Tue, 24 Jan 2012 08:34:42 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP
	id q0OFXS97018954
	for <qemu-devel@nongnu.org>; Tue, 24 Jan 2012 08:33:29 -0700
Message-ID: <4F1ECF46.8050707@us.ibm.com>
Date: Tue, 24 Jan 2012 09:33:26 -0600
From: Anthony Liguori <aliguori@us.ibm.com>
MIME-Version: 1.0
References: <cover.1326972302.git.jan.kiszka@siemens.com>	<6a48ffaaa732b2142c1b5030178f2d4a0fa499fe.1326972302.git.jan.kiszka@siemens.com>	<20120119180851.GA19099@amt.cnet>
	<4F1866E0.7010900@web.de> <4F1EBAAF.8040808@redhat.com>
In-Reply-To: <4F1EBAAF.8040808@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v8 18/18] kvm: Activate in-kernel irqchip
	support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>, Jan Kiszka <jan.kiszka@web.de>

On 01/24/2012 08:05 AM, Avi Kivity wrote:
> On 01/19/2012 08:54 PM, Jan Kiszka wrote:
>> Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
>> the qtree (different device model names).
>
> That was my biggest objection to the previous iterations.  Later
> versions changed to use an attribute (selecting the backend).  What
> happened now?

They have different *type* names.  They can have the same *object* name.

All user interaction with a device should be through object name.  The type name 
is merely an implementation detail.

Regards,

Anthony Liguori

>