From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, marcel@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: Tue, 7 Mar 2017 17:19:23 +0800 [thread overview]
Message-ID: <20170307091923.GA31585@pxdev.xzpeter.org> (raw)
In-Reply-To: <1488877751-13419-1-git-send-email-jasowang@redhat.com>
On Tue, Mar 07, 2017 at 05:09:11PM +0800, Jason Wang wrote:
> After commit 96a8821d2141 ("virtio: unbreak virtio-pci with IOMMU
> after caching ring translations"), IOMMU was required to be created in
> advance. This is because we can only get the correct dma_as after pci
> IOMMU (e.g intel_iommu) was initialized. This is suboptimal and
> inconvenient for user. This patch releases this by:
>
> - introduce a bus_master_ready method for PCIDeviceClass and trigger
> this during pci_init_bus_master
> - implement virtio-pci method and 1) reset the dma_as 2) re-register
> the memory listener to the new dma_as
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
next prev parent reply other threads:[~2017-03-07 9:19 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 [this message]
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
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=20170307091923.GA31585@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).