From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: yamahata@valinux.co.jp, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci: pass bridge update to secondary bus
Date: Wed, 7 Jul 2010 20:36:20 +0300 [thread overview]
Message-ID: <20100707173620.GB15597@redhat.com> (raw)
In-Reply-To: <AANLkTin_vG_LSIXf8AnE61-va8XiUydx6rAfnK-VJT4i@mail.gmail.com>
On Wed, Jul 07, 2010 at 05:31:39PM +0000, Blue Swirl wrote:
> On Tue, Jul 6, 2010 at 11:23 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > bridge config write should trigger updates
> > on the secondary bus. never on the primary bus.
>
> If this is true, shouldn't updates happen on all buses from secondary
> to subordinate? Do we know which of these are immediately below
> primary bus?
pci_bridge_update_mappings does this already.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> >
> > Compile-tested only.
> > Isaku Yamahata, could you review this please?
> > You wrote the code, and you seem to have some bridged setups.
> >
> > hw/pci.c | 4 +++-
> > 1 files changed, 3 insertions(+), 1 deletions(-)
> >
> > diff --git a/hw/pci.c b/hw/pci.c
> > index 926cf63..011d83e 100644
> > --- a/hw/pci.c
> > +++ b/hw/pci.c
> > @@ -1513,7 +1513,9 @@ static void pci_bridge_write_config(PCIDevice *d,
> > /* memory base/limit, prefetchable base/limit and
> > io base/limit upper 16 */
> > ranges_overlap(address, len, PCI_MEMORY_BASE, 20)) {
> > - pci_bridge_update_mappings(d->bus);
> > + PCIBridge *s = container_of(d, PCIBridge, dev);
> > + PCIBus *secondary_bus = &s->bus;
> > + pci_bridge_update_mappings(secondary_bus);
> > }
> > }
> >
> > --
> > 1.7.2.rc0.14.g41c1c
> >
> >
prev parent reply other threads:[~2010-07-07 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 11:23 [Qemu-devel] [PATCH] pci: pass bridge update to secondary bus Michael S. Tsirkin
2010-07-07 2:04 ` [Qemu-devel] " Isaku Yamahata
2010-07-08 13:25 ` Michael S. Tsirkin
2010-07-07 17:31 ` [Qemu-devel] " Blue Swirl
2010-07-07 17:36 ` Michael S. Tsirkin [this message]
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=20100707173620.GB15597@redhat.com \
--to=mst@redhat.com \
--cc=blauwirbel@gmail.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 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.