public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: tugouxp <13824125580@163.com>
To: qemu-devel@nongnu.org
Subject: Contradiction in Intel IOMMU Two‑Stage Translation: Stage 1 Mapping Requirements Leaked to Hypervisor Due to Host‑Side Driver Interface.
Date: Thu, 26 Mar 2026 14:54:56 +0800 (CST)	[thread overview]
Message-ID: <c304de5.6160.19d28ecbbd0.Coremail.13824125580@163.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

Hi folks:
In a two-stage translation scheme, the first stage should be hidden inside the VM driver. For example, the emulated hardware of the VM needs to use Stage 1 to map GVA (or GIOVA) to GPA, while Stage 2 should be handled by the hypervisor. I understand this principle.

However, in the current Intel IOMMU implementation of two-stage translation, it seems that both Stage 2 and Stage 1 require directly invoking driver interfaces in the host hypervisor. This approach exposes the VM’s internal Stage 1 mapping requirements to the hypervisor, which creates a contradiction.

How should QEMU and Linux implement this properly?

Best wishes to you!

zlcao.

[-- Attachment #2: Type: text/html, Size: 2628 bytes --]

                 reply	other threads:[~2026-03-26  6:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c304de5.6160.19d28ecbbd0.Coremail.13824125580@163.com \
    --to=13824125580@163.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