All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 0/2] qemu-help: improve -device command line help
Date: Mon, 29 Jul 2013 13:27:02 +0200	[thread overview]
Message-ID: <51F65186.8020004@redhat.com> (raw)
In-Reply-To: <1375084808.14541.12.camel@localhost.localdomain>

Il 29/07/2013 10:00, Marcel Apfelbaum ha scritto:
> On Mon, 2013-07-29 at 09:36 +0200, Paolo Bonzini wrote:
>> Il 28/07/2013 11:14, Marcel Apfelbaum ha scritto:
>>> Categories:
>>> Assembly   - hosts/hubs/...
>>
>> A lot of these seem to fit in a "bridge" category.
> I wanted to group in a category as much as possible having in
> mind the user shall "grep" by category to find devices.
> My goal is a top category with devices that are not nodes and
> are used as a way to combine other devices.
>>
>> I'm not sure why usbhost is in the assembly category though.  Also, why
>> is this the default category for isa and i2c devices?
> The same argument as above. I am looking for top devices and not for
> their type 

USB host is a leaf device.  As to ISA and I2C, which devices exactly are
using the default you're setting here?  Are they really bridge- or
controller-type device?

>>> Management - controllers 
>>
>> AHCI is storage.
> Thanks, it looked like management to me.
> Devices in management category shall control other devices.
> It looked like a fit for me.   

Yeah, it does, but then the same is true for all SCSI HBAs.

>> applesmc is something like a microcontroller ("misc"?).
> Thanks, I'll move to misc
>>
>> Everything else in this category is USB host controllers, I think it
>> deserves a special category since USB devices are generally somewhat
>> self-explanatory (hubs too).
> I didn't want to include the "USB" keyword, because the user will be lost
> when filtering by this word. The goal is to help the user to concentrate 
> on a specific "category". Maybe USB-Controller ?

Maybe two categories (USB | Controller)?  There is also difference
between storage controllers and storage devices (i.e. disks).

I think assembly and management can be merged into a single
"controller/hub/bridge" category.  You can then use multiple categories
for HBAs, for AHCI, etc.

Paolo

  reply	other threads:[~2013-07-29 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-28  9:14 [Qemu-devel] [PATCH 0/2] qemu-help: improve -device command line help Marcel Apfelbaum
2013-07-28  9:14 ` [Qemu-devel] [PATCH 1/2] qemu-help: Sort devices by logical functionality Marcel Apfelbaum
2013-07-28 12:45   ` Michael S. Tsirkin
2013-07-28  9:14 ` [Qemu-devel] [PATCH 2/2] devices: Associate devices to their logical category Marcel Apfelbaum
2013-07-28 12:46 ` [Qemu-devel] [PATCH 0/2] qemu-help: improve -device command line help Michael S. Tsirkin
2013-07-29  7:36 ` Paolo Bonzini
2013-07-29  8:00   ` Marcel Apfelbaum
2013-07-29 11:27     ` Paolo Bonzini [this message]
2013-07-29 11:39       ` Marcel Apfelbaum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F65186.8020004@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=marcel.a@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.