qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 4/8] qdev/core: bus list
Date: Tue, 30 Jun 2009 15:36:09 -0500	[thread overview]
Message-ID: <4A4A7739.3030806@codemonkey.ws> (raw)
In-Reply-To: <4A4A731D.5020306@redhat.com>

Gerd Hoffmann wrote:
> On 06/30/09 21:49, Anthony Liguori wrote:
>> I think it's a perfectly valid suggestion that we should identify buses
>> based on the their location in the tree to users verses a number
>> generated based on some hashing algorithm.
> >
>> A tree location has meaning to a user. A random integer doesn't.
>
> Well.  Depends on the bus I think.  About PCI devices the usual user 
> probably thinks in terms of "$bus:$slot.$function", which includes a 
> bus number.

But if you think of SCSI as a bus, then it makes more sense to enumerate 
each SCSI bus by the tree location (which would end up being the PCI 
location) than a made up number.

> Speaking of PCI: the PCI bus number (aka PCIBus->bus_num) has nothing 
> to do with the more or less random bus number introduced by the (now 
> dropped) patch (aka PCIBus->qdev.busnr).

Yup.

> Which indicates that it is probably less confusing to have the bus 
> implementation handle the enumeration of busses.  If it makes sense 
> for the bus in question of course.  sysbus probably doesn't care ;)

That's probably a good point.

Regards,

Anthony Liguori

  reply	other threads:[~2009-06-30 20:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  9:25 [Qemu-devel] [PATCH 0/7] qdev patches, batch #1 Gerd Hoffmann
2009-06-30  9:25 ` [Qemu-devel] [PATCH 1/8] qdev: update pci device registration Gerd Hoffmann
2009-06-30  9:25 ` [Qemu-devel] [PATCH 2/8] qdev: replace bus_type enum with bus_info struct Gerd Hoffmann
2009-06-30  9:25 ` [Qemu-devel] [PATCH 3/8] qdev: remove DeviceType Gerd Hoffmann
2009-06-30  9:25 ` [Qemu-devel] [PATCH 4/8] qdev/core: bus list Gerd Hoffmann
2009-06-30 11:18   ` Paul Brook
2009-06-30 16:55     ` Markus Armbruster
2009-06-30 17:21       ` Paul Brook
2009-06-30 19:26         ` Markus Armbruster
2009-06-30 19:49           ` Anthony Liguori
2009-06-30 20:18             ` Gerd Hoffmann
2009-06-30 20:36               ` Anthony Liguori [this message]
2009-07-01  0:25               ` Paul Brook
2009-07-01  6:32                 ` Gerd Hoffmann
2009-07-01  0:12             ` Markus Armbruster
2009-07-01  0:29               ` Paul Brook
2009-06-30  9:25 ` [Qemu-devel] [PATCH 5/8] qdev/core: add monitor command to list all drivers Gerd Hoffmann
2009-06-30  9:26 ` [Qemu-devel] [PATCH 6/8] qdev/pci: misc fixes Gerd Hoffmann
2009-06-30 11:25   ` Paul Brook
2009-06-30 16:51     ` Markus Armbruster
2009-06-30  9:26 ` [Qemu-devel] [PATCH 7/8] qdev: convert es1370 Gerd Hoffmann
2009-06-30  9:26 ` [Qemu-devel] [PATCH 8/8] qdev: convert ac97 Gerd Hoffmann

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=4A4A7739.3030806@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=paul@codesourcery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).