qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv2-RFC 2/2] pci: add standard bridge device
Date: Mon, 20 Feb 2012 01:44:34 +0200	[thread overview]
Message-ID: <20120219234433.GA29703@redhat.com> (raw)
In-Reply-To: <20120219145707.GC16620@redhat.com>

On Sun, Feb 19, 2012 at 04:57:07PM +0200, Michael S. Tsirkin wrote:
> On Fri, Feb 17, 2012 at 02:25:56PM +0100, Gerd Hoffmann wrote:
> >   Hi,
> > 
> > > +    /* If we don't specify the name, the bus will be addressed as <id>.0, where
> > > +     * id is the parent id.  But it seems more natural to address the bus using
> > > +     * the parent device name. */
> > > +    if (dev->qdev.id && *dev->qdev.id) {
> > > +        br->bus_name = dev->qdev.id;
> > > +    }
> > 
> > That makes the bridge behave different than everybody else.
> > Not a good idea IMHO.
> > 
> > cheers,
> >   Gerd
> 
> Everybody else has names built up according to an undocumented scheme
> which no one can figure out without reading code, so no one uses them.
> We need to fix that, but there is, generally, no need for these names
> so it stayed low priority.
> 
> With the bridge people must use the id to connect devices to it,
> so name must be a sane one.

I just sent the patch making bus id for bridges
follow the value set by the user.
That will make the bridge behave in the same way
as everybody else :)

> -- 
> MST

  reply	other threads:[~2012-02-19 23:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:15 [Qemu-devel] [PATCHv2-RFC 0/2] RFC: standard pci bridge device Michael S. Tsirkin
2012-02-13  9:15 ` [Qemu-devel] [PATCHv2-RFC 1/2] shpc: standard hot plug controller Michael S. Tsirkin
2012-02-13 10:03   ` Isaku Yamahata
2012-02-13 11:49     ` Michael S. Tsirkin
2012-02-13 14:30       ` Isaku Yamahata
2012-02-13 14:49         ` Michael S. Tsirkin
2012-02-17 13:20   ` Gerd Hoffmann
2012-02-13  9:16 ` [Qemu-devel] [PATCHv2-RFC 2/2] pci: add standard bridge device Michael S. Tsirkin
2012-02-17 13:25   ` Gerd Hoffmann
2012-02-19 14:57     ` Michael S. Tsirkin
2012-02-19 23:44       ` Michael S. Tsirkin [this message]
2012-02-17 13:33   ` Gerd Hoffmann
2012-02-20 22:40     ` Michael S. Tsirkin
2012-02-21  8:02       ` Gerd Hoffmann
2012-02-13  9:33 ` [Qemu-devel] [PATCH RFC] seabios: add OSHP method stub Michael S. Tsirkin
2012-02-14  0:34   ` Kevin O'Connor
2012-02-14  0:43     ` Michael S. Tsirkin
2012-02-14  0:48       ` Kevin O'Connor
2012-02-14  1:09         ` Michael S. Tsirkin
2012-02-14 12:49           ` Paul Brook
2012-02-14 13:37             ` Michael S. Tsirkin
2012-02-14 13:47               ` Paul Brook
2012-02-14 14:11                 ` Michael S. Tsirkin
2012-02-29 11:25   ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2012-02-13  9:38 ` [Qemu-devel] [PATCHv2-RFC 0/2] RFC: standard pci bridge device Wen Congyang
2012-02-13  9:56   ` Michael S. Tsirkin

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=20120219234433.GA29703@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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).