[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 6/8] intel_iommu: support device iotlb descr
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [RFC PATCH 6/8] intel_iommu: support device iotlb descriptor |
Date: |
Wed, 30 Mar 2016 13:21:23 +0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Wed, Mar 30, 2016 at 01:08:45PM +0800, Jason Wang wrote:
[...]
> >> + } else {
> >> + sz = VTD_PAGE_SIZE;
> >> + }
> >> +
> >> + entry.target_as = &vtd_dev_as->as;
> >> + entry.addr_mask = sz - 1;
> >> + entry.iova = addr;
> >> + memory_region_notify_iommu(entry.target_as->root, entry);
> > Here, we seems to be posting this invalidation to all registered
> > notifiers.
>
> Yes, but only for a device specified address space.
>
> > Since this is a device-tlb invalidation, and we should
> > know which device (BDF) that we should invalidate, is there any way
> > that we can directly route this info to that specific device?
>
> Looks like the codes has already done this, the target_as was found by
> bus num and devfn.
Yes, seems you are right. :)
-- peterx
- [Qemu-devel] [RFC PATCH 3/8] intel_iommu: allocate new key when creating new address space, (continued)
- [Qemu-devel] [RFC PATCH 3/8] intel_iommu: allocate new key when creating new address space, Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 1/8] virtio: convert to use DMA api, Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 4/8] exec: introduce address_space_get_iotlb_entry(), Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 5/8] virtio-pci: address space translation service (ATS) support, Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 6/8] intel_iommu: support device iotlb descriptor, Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 7/8] memory: handle alias for iommu notifier, Jason Wang, 2016/03/24
- [Qemu-devel] [RFC PATCH 8/8] vhost_net: device IOTLB support, Jason Wang, 2016/03/24