From: Alex Williamson <alex.williamson@redhat.com>
To: "leohou@tom.com" <leohou@tom.com>
Cc: iommu <iommu@lists.linux.dev>, qemu-arm <qemu-arm@nongnu.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: vIOMMU&IOMMU gIOVA to HPA mapping
Date: Mon, 14 Nov 2022 09:18:02 -0700 [thread overview]
Message-ID: <20221114091802.6be5099e.alex.williamson@redhat.com> (raw)
In-Reply-To: <2022111420314945171759@tom.com>
On Mon, 14 Nov 2022 20:31:49 +0800
"leohou@tom.com" <leohou@tom.com> wrote:
> Hi，
> Here is my application scenario：
> 1. The NIC (Network Information Center) passes through to the VM(Virtual Machine);
> 2. The VM uses the user mode driver DPDK;
>
> Question:
> 1. vIOMMU maintains the mapping gIOVA->gPA, When do you use this gPA ?
QEMU in the host derives the hVA from the gPA. The vIOMMU driver in
QEMU is triggering the gIOVA to hVA mapping through vfio in the host.
> 2. Physical IOMMU maintains the GIOVA->HPA mapping ? If so, by what means (gIOVA -> HPA) mapping ?
As above, the vIOMMU in the guest provides gIOVA -> gPA, in QEMU we do
the gPA -> hVA, then vfio in the host kernel performs hVA -> hPA via
page pinning.
> 3. What does QEMU do in NIC pass-through address translation ？
The guest visible vIOMMU triggers MemoryListener notifications in QEMU
for the device address space, which insert and removes mappings to the
vfio layer below it. Thanks,
Alex
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
parent reply other threads:[~2022-11-14 16:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2022111420314945171759@tom.com>]
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=20221114091802.6be5099e.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=leohou@tom.com \
--cc=qemu-arm@nongnu.org \
--cc=virtualization@lists.linux-foundation.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).