From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MOvpp-0001hX-06
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 11:46:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MOvpk-0001d5-Hr
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 11:46:56 -0400
Received: from [199.232.76.173] (port=59404 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MOvpk-0001d0-Ci
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 11:46:52 -0400
Received: from rv-out-0708.google.com ([209.85.198.249]:11843)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MOvpk-0007cm-0Y
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 11:46:52 -0400
Received: by rv-out-0708.google.com with SMTP id c5so5686rvf.2
	for <qemu-devel@nongnu.org>; Thu, 09 Jul 2009 08:46:51 -0700 (PDT)
Message-ID: <4A5610E6.80507@codemonkey.ws>
Date: Thu, 09 Jul 2009 10:46:46 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: add driver class support.
References: <1247144544-8885-1-git-send-email-kraxel@redhat.com>	<200907091419.11248.paul@codesourcery.com>	<4A55F30C.9000502@redhat.com>	<200907091448.59926.paul@codesourcery.com>
	<4A55FE23.4090205@redhat.com>
In-Reply-To: <4A55FE23.4090205@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15; 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: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org

Gerd Hoffmann wrote:
> On 07/09/09 15:48, Paul Brook wrote:
>> On Thursday 09 July 2009, Gerd Hoffmann wrote:
>
>>> I don't think this will work out in the general case.  Some devices 
>>> have
>>> properties which can be used for that, i.e. network cards have a mac
>>> address (no attribute yet but I expect it will come some day).  Not
>>> every device class has specific properties you can use to identify them
>>> though.  How would you identify a sound card for example?
>>
>> Ok, put it annother way: Why do you need to identify them? Why would 
>> libvirt
>> care whether a device is (say) a sound card or a VGA adapter?
>
> Because libvirt-based applications want present that to the user?
>
> The usual GUI workflow for adding devices is a two-step process:  
> First pick the device class, then pick the actual device from a 
> (short) list.

Wouldn't the definitions of classes be something that the GUI would want 
to define?

I think we do want a way to say that this device provides graphics 
capability and have that exposed to through the monitor.  But we also 
have to consider the case where a single device exposes multiple types 
of capabilities.

Regards,

Anthony Liguori