From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, vkaplans@redhat.com,
wexu@redhat.com, cornelia.huck@de.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4 10/10] vhost_net: device IOTLB support
Date: Wed, 11 Jan 2017 10:34:16 +0800 [thread overview]
Message-ID: <3f506d7a-d8f2-795e-43c8-06e9c16c2c6a@redhat.com> (raw)
In-Reply-To: <20170110065459-mutt-send-email-mst@kernel.org>
On 2017年01月10日 12:55, Michael S. Tsirkin wrote:
> On Fri, Dec 30, 2016 at 06:09:19PM +0800, Jason Wang wrote:
>> This patches implements Device IOTLB support for vhost kernel. This is
>> done through:
>>
>> 1) switch to use dma helpers when map/unmap vrings from vhost codes
>> 2) introduce a set of VhostOps to:
>> - setting up device IOTLB request callback
>> - processing device IOTLB request
>> - processing device IOTLB invalidation
>> 2) kernel support for Device IOTLB API:
>>
>> - allow vhost-net to query the IOMMU IOTLB entry through eventfd
>> - enable the ability for qemu to update a specified mapping of vhost
>> - through ioctl.
>> - enable the ability to invalidate a specified range of iova for the
>> device IOTLB of vhost through ioctl. In x86/intel_iommu case this is
>> triggered through iommu memory region notifier from device IOTLB
>> invalidation descriptor processing routine.
>>
>> With all the above, kernel vhost_net can co-operate with userspace
>> IOMMU. For vhost-user, the support could be easily done on top by
>> implementing the VhostOps.
>>
>> Cc: Michael S. Tsirkin<mst@redhat.com>
>> Signed-off-by: Jason Wang<jasowang@redhat.com>
> Specifically this patch is the one causing issues.
>
>
Yes, this is because it tries to enable device IOTLB for vhost-user.
Will post a new version for this patch.
Thanks
next prev parent reply other threads:[~2017-01-11 2:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 10:09 [Qemu-devel] [PATCH V4 00/10] vhost device IOTLB support Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 01/10] virtio: convert to use DMA api Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 02/10] intel_iommu: name vtd address space with devfn Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 03/10] intel_iommu: allocate new key when creating new address space Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 04/10] exec: introduce address_space_get_iotlb_entry() Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 05/10] intel_iommu: support device iotlb descriptor Jason Wang
2017-01-03 3:37 ` Peter Xu
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 06/10] virtio-pci: address space translation service (ATS) support Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 07/10] acpi: add ATSR for q35 Jason Wang
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 08/10] memory: handle alias for iommu notifier Jason Wang
2017-01-03 3:42 ` Peter Xu
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 09/10] memory: handle alias in memory_region_is_iommu() Jason Wang
2017-01-03 3:42 ` Peter Xu
2016-12-30 10:09 ` [Qemu-devel] [PATCH V4 10/10] vhost_net: device IOTLB support Jason Wang
2017-01-10 4:55 ` Michael S. Tsirkin
2017-01-11 2:34 ` Jason Wang [this message]
2017-01-10 4:54 ` [Qemu-devel] [PATCH V4 00/10] vhost " Michael S. Tsirkin
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=3f506d7a-d8f2-795e-43c8-06e9c16c2c6a@redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.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 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).