From: Peter Xu <peterx@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, yi.l.liu@intel.com,
"\\ Michael S . Tsirkin \\ " <mst@redhat.com>,
Jintack Lim <jintack@cs.columbia.edu>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: make sure its init before PCI dev
Date: Thu, 23 Feb 2017 16:16:16 +0800 [thread overview]
Message-ID: <20170223081616.GI4015@pxdev.xzpeter.org> (raw)
In-Reply-To: <7cd743a2-b4c2-1d96-892e-c3a7db07da16@redhat.com>
On Thu, Feb 23, 2017 at 10:10:57AM +0200, Marcel Apfelbaum wrote:
> On 02/23/2017 05:06 AM, Peter Xu wrote:
> >On Wed, Feb 22, 2017 at 10:30:47AM -0700, Alex Williamson wrote:
> >>On Wed, 22 Feb 2017 13:49:25 +0800
> >>Peter Xu <peterx@redhat.com> wrote:
> >>
> >>>Intel vIOMMU devices are created with "-device" parameter, while here
> >>>actually we need to make sure this device will be created before some
> >>>other PCI devices (like vfio-pci devices) so that we know iommu_fn will
> >>>be setup correctly before realizations of those PCI devices.
> >>>
> >>>Here we do explicit check to make sure intel-iommu device will be inited
> >>>before all the rest of the PCI devices. This is done by checking against
> >>>the devices dangled under current root PCIe bus and we should see
> >>>nothing there besides integrated ICH9 ones.
>
> Hi,
>
> Commit b86eacb8 (hw/pci: delay bus_master_enable_region initialization)
> creates the IOMMU memory region at machine_done time so the
> devices creation order wouldn't matter.
>
> I don't think we use the iommu_fn before machine_done.
> What have I missed?
Hi, Marcel,
The problem is that vfio-pci will need to fetch the pci address space
during realization (pci_device_iommu_address_space() is called in
vfio_realize()).
Any thoughts? Thanks,
-- peterx
next prev parent reply other threads:[~2017-02-23 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 5:49 [Qemu-devel] [PATCH] intel_iommu: make sure its init before PCI dev Peter Xu
2017-02-22 11:42 ` Jintack Lim
2017-02-22 13:37 ` Jintack Lim
2017-02-23 2:35 ` Peter Xu
2017-02-22 17:30 ` Alex Williamson
2017-02-23 3:06 ` Peter Xu
2017-02-23 3:24 ` Alex Williamson
2017-02-23 5:42 ` Peter Xu
2017-02-23 23:26 ` Michael S. Tsirkin
2017-02-23 8:10 ` Marcel Apfelbaum
2017-02-23 8:16 ` Peter Xu [this message]
2017-02-23 12:02 ` Marcel Apfelbaum
2017-02-23 15:35 ` Alex Williamson
2017-02-28 14:37 ` Marcel Apfelbaum
2017-03-09 12:31 ` Paolo Bonzini
2017-03-09 15:29 ` Michael S. Tsirkin
2017-03-09 15:34 ` Paolo Bonzini
2017-02-23 23:21 ` Michael S. Tsirkin
2017-02-24 2:45 ` Peter Xu
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=20170223081616.GI4015@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jintack@cs.columbia.edu \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
/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.