All of
 help / color / mirror / Atom feed
From: Stefano Stabellini <>
To: Roman Skakun <>
Cc: Stefano Stabellini <>,
	Julien Grall <>,
	 Bertrand Marquis <>,
	 Andrii Anisov <>,
	Roman Skakun <>
Subject: Re: Disable IOMMU in Dom0
Date: Tue, 31 Aug 2021 14:50:22 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2108311444310.18862@sstabellini-ThinkPad-T480s> (raw)
In-Reply-To: <>

On Tue, 31 Aug 2021, Roman Skakun wrote:
> Hi, Stefano!
> I have seen your negotiation of disabling xen-swiotlb for devices which are controlled by IOMMU in Dom0:
> As I was thinking to create a common implementation because I have the issue
> when device controlled by IOMMU using xen-swiotlb fops and bounce buffer as the result.
> Do you have any future plans to finish implementation for upstream?

Hi Roman,

The feature is already upstream in Linux as f5079a9a2, and the new
feature flags are XENFEAT_direct_mapped and XENFEAT_not_direct_mapped.

If you have a setup where Dom0 is not 1:1 mapped (which is not currently
possible with upstream Xen but it is possible with cache coloring) and
uses the IOMMU to make device DMA work like regular DomUs, then passing
XENFEAT_not_direct_mapped to Linux would make it work. Without
XENFEAT_not_direct_mapped, Linux would try to use swiotlb-xen which has
code that relies on Linux being 1:1 mapped to work properly.

Is that the same problem that you have, or is dom0 1:1 mapped in your
case? If dom0 is 1:1 mapped then swiotlb-xen should work regardless of
whether the IOMMU is enabled or disabled.

I hope this helps.



  reply	other threads:[~2021-08-31 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 19:54 Disable IOMMU in Dom0 Roman Skakun
2021-08-31 21:50 ` Stefano Stabellini [this message]
2021-09-01  9:59   ` Roman Skakun
2021-09-01 10:22     ` Julien Grall
2021-09-09 14:25       ` Roman Skakun
2021-09-09 19:53         ` Stefano Stabellini

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2108311444310.18862@sstabellini-ThinkPad-T480s \ \ \ \ \ \ \ \

* 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 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.