* [Qemu-devel] virtio + virtq + iommu
@ 2014-07-08 15:21 Anshul Makkar
2014-07-09 14:18 ` Anshul Makkar
2014-07-18 10:10 ` Anshul Makkar
0 siblings, 2 replies; 3+ messages in thread
From: Anshul Makkar @ 2014-07-08 15:21 UTC (permalink / raw)
To: qemu-devel
Hi,
Was tracing the buffer handling code flow after the kick has been
initiated from the guest in case of virtio.
Found this function
cpu_physical_memory_map->address_space_map->address_space_translate
which calls address_space_translate_internal and iommu->translate (get
the translation from TLB) to get the corresponding host virtual
address where I think the packet buffer is mapped to (from guest
physical to host virtual).
So, should I conclude that there is no hardware IOMMU involved in this
translation. QEMU maintains its own TLB and translation mapping which
is used. Or iommu->translate leads to hardware MMU call.
We are developing a high speed packet transfer mechanism using
infiniband cards. So, trying to analyse every possible bottleneck.
Confused here, please suggest.
Anshul Makkar
www.justkernel.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] virtio + virtq + iommu
2014-07-08 15:21 [Qemu-devel] virtio + virtq + iommu Anshul Makkar
@ 2014-07-09 14:18 ` Anshul Makkar
2014-07-18 10:10 ` Anshul Makkar
1 sibling, 0 replies; 3+ messages in thread
From: Anshul Makkar @ 2014-07-09 14:18 UTC (permalink / raw)
To: qemu-devel
Hi,
Any suggestions.
Anshul Makkar
On Tue, Jul 8, 2014 at 5:21 PM, Anshul Makkar
<anshul.makkar@profitbricks.com> wrote:
> Hi,
>
> Was tracing the buffer handling code flow after the kick has been
> initiated from the guest in case of virtio.
>
> Found this function
> cpu_physical_memory_map->address_space_map->address_space_translate
> which calls address_space_translate_internal and iommu->translate (get
> the translation from TLB) to get the corresponding host virtual
> address where I think the packet buffer is mapped to (from guest
> physical to host virtual).
>
> So, should I conclude that there is no hardware IOMMU involved in this
> translation. QEMU maintains its own TLB and translation mapping which
> is used. Or iommu->translate leads to hardware MMU call.
>
> We are developing a high speed packet transfer mechanism using
> infiniband cards. So, trying to analyse every possible bottleneck.
>
> Confused here, please suggest.
>
> Anshul Makkar
> www.justkernel.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] virtio + virtq + iommu
2014-07-08 15:21 [Qemu-devel] virtio + virtq + iommu Anshul Makkar
2014-07-09 14:18 ` Anshul Makkar
@ 2014-07-18 10:10 ` Anshul Makkar
1 sibling, 0 replies; 3+ messages in thread
From: Anshul Makkar @ 2014-07-18 10:10 UTC (permalink / raw)
To: qemu-devel
Further adding on to it.
iotlb = mr->iommu_ops->translate(mr, addr) in address_space_translate
to get the translation from the tlb.
What I found is that the "iommu_ops->translate" is assigned a
function pointer only for alpha/typhoon and ppc/spapr. What about x86.
Are we using any of these architectures for emulating
iommu for x86 ?
Anshul Makkar
On Tue, Jul 8, 2014 at 5:21 PM, Anshul Makkar
<anshul.makkar@profitbricks.com> wrote:
> Hi,
>
> Was tracing the buffer handling code flow after the kick has been
> initiated from the guest in case of virtio.
>
> Found this function
> cpu_physical_memory_map->address_space_map->address_space_translate
> which calls address_space_translate_internal and iommu->translate (get
> the translation from TLB) to get the corresponding host virtual
> address where I think the packet buffer is mapped to (from guest
> physical to host virtual).
>
> So, should I conclude that there is no hardware IOMMU involved in this
> translation. QEMU maintains its own TLB and translation mapping which
> is used. Or iommu->translate leads to hardware MMU call.
>
> We are developing a high speed packet transfer mechanism using
> infiniband cards. So, trying to analyse every possible bottleneck.
>
> Confused here, please suggest.
>
> Anshul Makkar
> www.justkernel.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-07-18 10:10 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-08 15:21 [Qemu-devel] virtio + virtq + iommu Anshul Makkar
2014-07-09 14:18 ` Anshul Makkar
2014-07-18 10:10 ` Anshul Makkar
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.