From: "Daniel P. Berrange" <berrange@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Name the default PCI bus "pci.0" on all architectures
Date: Thu, 20 May 2010 11:00:39 +0100 [thread overview]
Message-ID: <20100520100039.GB28087@redhat.com> (raw)
In-Reply-To: <AANLkTinpvHROo-QZ2kfPr1P8sfIIrO-bTEC0XbiuYKvS@mail.gmail.com>
On Wed, May 19, 2010 at 10:19:06PM +0300, Blue Swirl wrote:
> On 5/19/10, Daniel P. Berrange <berrange@redhat.com> wrote:
> > The system emulators for each arch are using inconsistent
> > naming for the default PCI bus "pci" vs "pci.0". Since it
> > is conceivable we'll have multiple PCI buses in the future
> > standardize on "pci.0" for all architectures. This ensures
> > mgmt apps can rely on a name when assigning PCI devices an
> > address on the bus using eg '-device e1000,bus=pci.0,addr=3'
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > hw/grackle_pci.c | 2 +-
> > hw/gt64xxx.c | 2 +-
> > hw/ppc4xx_pci.c | 2 +-
> > hw/ppce500_pci.c | 2 +-
> > hw/prep_pci.c | 2 +-
> > hw/sh_pci.c | 2 +-
> > hw/unin_pci.c | 4 ++--
> > hw/versatile_pci.c | 2 +-
>
> Missing hw/apb_pci.c.
Ah yes, don't know how I missed that. Have posted another version
of this patch with that included
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-05-20 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 16:42 [Qemu-devel] [PATCH] Name the default PCI bus "pci.0" on all architectures Daniel P. Berrange
2010-05-19 19:19 ` Blue Swirl
2010-05-20 10:00 ` Daniel P. Berrange [this message]
2010-05-28 19:39 ` Paul Brook
2010-05-29 5:13 ` Markus Armbruster
2010-06-02 15:13 ` Paul Brook
2010-06-11 13:00 ` Markus Armbruster
2010-06-11 14:28 ` Paul Brook
2010-06-02 14:12 ` Daniel P. Berrange
2010-06-02 15:10 ` Paul Brook
2010-06-02 21:03 ` Gerd Hoffmann
2010-06-03 5:45 ` Paul Brook
2010-06-03 10:14 ` Andreas Färber
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=20100520100039.GB28087@redhat.com \
--to=berrange@redhat.com \
--cc=blauwirbel@gmail.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).