From: Christoph Hellwig <hch@infradead.org>
To: Daniel Drake <drake@endlessm.com>
Cc: Jon Derrick <jonathan.derrick@intel.com>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Bjorn Helgaas <helgaas@kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: [PATCH 1/1] iommu/vt-d: use DMA domain for real DMA devices and subdevices
Date: Sun, 12 Apr 2020 00:35:29 -0700 [thread overview]
Message-ID: <20200412073529.GA13784@infradead.org> (raw)
In-Reply-To: <CAD8Lp442LO1Sq5xpKOaRUKLsEyGbou4TiHQrDdnMbCOV-TG0+g@mail.gmail.com>
On Sun, Apr 12, 2020 at 11:50:09AM +0800, Daniel Drake wrote:
> > different addressing capabilities and some require translation. Instead we can
> > put the real DMA dev and any subdevices on the DMA domain. This change assigns
> > subdevices to the DMA domain, and moves the real DMA device to the DMA domain
> > if necessary.
>
> Have you tested this with the real DMA device in identity mode?
> It is not quite working for me. (Again, I'm not using VMD here, but
> have looked closely and believe we're working under the same
> constraints)
So if you are not using VMD how does this matter for upstream?
next prev parent reply other threads:[~2020-04-12 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 19:17 [PATCH 0/1] Real DMA dev DMA domain patch Jon Derrick
2020-04-09 19:17 ` [PATCH 1/1] iommu/vt-d: use DMA domain for real DMA devices and subdevices Jon Derrick
2020-04-10 1:22 ` Lu Baolu
2020-04-13 2:25 ` Daniel Drake
2020-04-13 2:48 ` Lu Baolu
2020-04-13 16:08 ` Derrick, Jonathan
2020-04-18 12:13 ` Joerg Roedel
2020-04-12 3:50 ` Daniel Drake
2020-04-12 7:35 ` Christoph Hellwig [this message]
2020-04-13 16:08 ` Derrick, Jonathan
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=20200412073529.GA13784@infradead.org \
--to=hch@infradead.org \
--cc=baolu.lu@linux.intel.com \
--cc=drake@endlessm.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathan.derrick@intel.com \
--cc=joro@8bytes.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@endlessm.com \
/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).