From: Isaku Yamahata <yamahata@valinux.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 1/2] pci/bridge: allocate PCIBus dynamically for PCIBridge.
Date: Fri, 9 Jul 2010 11:07:37 +0900 [thread overview]
Message-ID: <20100709020737.GB22818@valinux.co.jp> (raw)
In-Reply-To: <20100708164934.GB4392@redhat.com>
On Thu, Jul 08, 2010 at 07:49:35PM +0300, Michael S. Tsirkin wrote:
> > > > - to eliminate assumption of pci_bus_new().
> > > > pci_bus_new() assumes that its pci segment is 0.
> > > > keep pci_bus_new() as a convenience wrapper of
> > > > pci_host_bus_new(segment = 0). Thus we can avoid fixing up
> > > > all the caller.
> > >
> > > We have a single caller, right? I think you mean pci_register_bus?
> > > So IIUC, you propose that we add pci_register_host_bus,
> > > and make pci_register_bus a compatibility wrapper?
> > > Sure, let's just add a comment this is deprecated.
> > >
> > > I am not sure why do we need an API to deal with secondary bus:
> > > it is always a part of the bridge, so all users can and should call
> > > pci_bridge_init?
> >
> > Okay, then how about the following?
> >
> > For root bus:
> > - pci_host_bus_new()/pci_host_bus_new_inplace()
> > qbus style api. pci segment must be specified.
> > New code should use this.
>
> I'd prefer a simple _init which works like _inplace.
> Allocating memory is simple enough for users.
I see. Then
- export PCIBus. This is necessary to tell its size.
- pci_host_bus_init()/pci_host_bus_cleanup()
which don't allocate memory.
> > - pci_bus_new()
> > qbus style API.
> > convenience wrapper for compatibility of
> > pci_host_bus_new(pci segment = 0)
> > In fact, the only current user piix_pci.c. It's easy to remove it.
> > - pci_register_bus()
> > old style API. deprecated.
> > It has been kept for compatibility so far.
> > This will be gradually replaced with pci_host_bus_new()
>
> Also, let's make these helpers inline: will make it possible
> to check code by comparing binary after changes.
Agreed.
>
> > For secondary bus:
> > - pci_bridge_init()
> > qdev style API.
> > New code should use this.
>
> Well - isn't the way we do this a bit backwards?
> I thought the idea was that each device has its own
> PCIDeviceInfo qdev structure, instead of the common pci-bridge.
>
> And then pci_bridge_init (or _setup to avoid reusing existing names)
> would be a common function that devices can reuse in their init
> functions..
Agreed and in fact I'm having such a patch.
Just I think it's next phase of clean up.
The patch series creates a library for pci bridge as you suggested before
and converts apb_pci.c and dec_pci.c into qdev.
>
> > - pci_{register, unregister}_secondary_bus():
> > old stype API. deprecated.
> > Keep them only for internal use in pci.c
> > or they can be easily removed or renamed for qdev style.
> >
> > For pci device:
> > - pci_create()
> > qdev style API.
> > The transitional function until completion of qdev conversion.
> > If the creation of a device tree from config file is implemented,
> > this function will be unnecessary.
> >
> > - pci_create_simple()
> > qdev style API.
> > convenience function = pci_create() + qdev_init_nofail()
> >
> > --
> > yamahata
>
--
yamahata
next prev parent reply other threads:[~2010-07-09 2:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 2:30 [Qemu-devel] [PATCH 0/2] pci: split out bridge code into pci_bridge Isaku Yamahata
2010-07-02 2:30 ` [Qemu-devel] [PATCH 1/2] pci/bridge: allocate PCIBus dynamically for PCIBridge Isaku Yamahata
2010-07-06 12:18 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-07 2:38 ` Isaku Yamahata
2010-07-07 11:47 ` Michael S. Tsirkin
2010-07-08 6:39 ` Isaku Yamahata
2010-07-08 14:04 ` Michael S. Tsirkin
2010-07-08 15:43 ` Isaku Yamahata
2010-07-08 16:49 ` Michael S. Tsirkin
2010-07-09 2:07 ` Isaku Yamahata [this message]
2010-07-16 1:46 ` Isaku Yamahata
2010-07-16 7:35 ` Michael S. Tsirkin
2010-07-02 2:30 ` [Qemu-devel] [PATCH 2/2] pci/bridge: split out pci bridge code into pci_bridge.c from pci.c Isaku Yamahata
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=20100709020737.GB22818@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=mst@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 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).