From: Peter Xu <peterx@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, qemu-devel@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V3] virtio: do not require IOMMU to be created in advance
Date: Wed, 8 Mar 2017 17:16:08 +0800 [thread overview]
Message-ID: <20170308091608.GE7135@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170308090945.GD7135@pxdev.xzpeter.org>
On Wed, Mar 08, 2017 at 05:09:45PM +0800, Peter Xu wrote:
> On Wed, Mar 08, 2017 at 10:17:09AM +0200, Marcel Apfelbaum wrote:
>
> [...]
>
> >
> > I am sorry I was not clear enough:
> > If a device is added after the system is up (hotplug), we cannot depend on the "machine_done"
> > event to enable "bus master".
> > This is why we have
> > if (qdev_hotplug)
> > pci_init_bus_master(pci_dev);
> >
> > The code you proposed changes the order, so this call is done *after* realize.
> >
> > My question was: What if any other device may require the bus_master_as
> > at realize time (and can be hot-plugged) ?
> > For example: hcd-ehci/hcd-ohci devices call pci_get_address_space()
> > and caches the bus_master_as.
>
> Oh, I didn't notice that there are other devices that used
> bus_master_as during realization. If so... Would this really work even
> without hot plug? Considering that bus_master_as won't be inited until
> machine done phase?
Please ignore my question... I think the answer is that these devices
are only caching the pointer of bus_master_as. So it won't really use
the address space before machine_done.
If so, IMHO moving pci_init_bus_master() after device specific
realize() is okay as well then, right?
Thanks,
-- peterx
next prev parent reply other threads:[~2017-03-08 9:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 9:09 [Qemu-devel] [PATCH V3] virtio: do not require IOMMU to be created in advance Jason Wang
2017-03-07 9:19 ` Peter Xu
2017-03-07 12:47 ` Marcel Apfelbaum
2017-03-08 2:43 ` Peter Xu
2017-03-08 3:15 ` Jason Wang
2017-03-08 8:17 ` Marcel Apfelbaum
2017-03-08 9:09 ` Peter Xu
2017-03-08 9:16 ` Peter Xu [this message]
2017-03-08 13:14 ` Marcel Apfelbaum
2017-03-08 9:57 ` Jason Wang
2017-03-08 8:24 ` Marcel Apfelbaum
2017-03-08 16:40 ` Igor Mammedov
2017-03-09 2:32 ` Jason Wang
2017-03-09 9:28 ` Igor Mammedov
2017-03-09 9:30 ` Paolo Bonzini
2017-03-09 9:58 ` Jason Wang
2017-03-09 10:05 ` Paolo Bonzini
2017-03-09 15:31 ` Michael S. Tsirkin
2017-03-09 15:32 ` Paolo Bonzini
2017-03-10 10:54 ` Jason Wang
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=20170308091608.GE7135@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).