From: Daniel Drake <drake@endlessm.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Joerg Roedel <joro@8bytes.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
jacob.jun.pan@linux.intel.com, "Tian,
Kevin" <kevin.tian@intel.com>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
iommu@lists.linux-foundation.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Derrick Jonathan <jonathan.derrick@intel.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 0/3] Replace private domain with per-group default domain
Date: Wed, 6 May 2020 10:09:37 +0800 [thread overview]
Message-ID: <CAD8Lp47E2CDmHTEGSpqYfxxKB4a+JY6VzZdL9e65P7YxqfL9Ag@mail.gmail.com> (raw)
In-Reply-To: <20200506015947.28662-1-baolu.lu@linux.intel.com>
On Wed, May 6, 2020 at 10:03 AM Lu Baolu <baolu.lu@linux.intel.com> wrote:
> https://lkml.org/lkml/2020/4/14/616
> [This has been applied in iommu/next.]
>
> Hence, there is no need to keep the private domain implementation
> in the Intel IOMMU driver. This patch series aims to remove it.
I applied these patches on top of Joerg's branch and confirmed that
they fix the issue discussed in the thread:
[PATCH v2] iommu/vt-d: consider real PCI device when checking if
mapping is needed
(the patch there is no longer needed)
Tested-by: Daniel Drake <drake@endlessm.com>
Thanks!
next prev parent reply other threads:[~2020-05-06 2:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 1:59 [PATCH v4 0/3] Replace private domain with per-group default domain Lu Baolu
2020-05-06 1:59 ` [PATCH v4 1/3] iommu/vt-d: Allow 32bit devices to uses DMA domain Lu Baolu
2020-05-06 1:59 ` [PATCH v4 2/3] iommu/vt-d: Allow PCI sub-hierarchy to use " Lu Baolu
2020-05-06 1:59 ` [PATCH v4 3/3] iommu/vt-d: Apply per-device dma_ops Lu Baolu
2020-05-06 2:09 ` Daniel Drake [this message]
2020-05-06 17:50 ` [PATCH v4 0/3] Replace private domain with per-group default domain Derrick, Jonathan
2020-05-10 23:16 ` Lu Baolu
2020-05-12 17:05 ` Jerry Snitselaar
2020-05-13 8:51 ` Joerg Roedel
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=CAD8Lp47E2CDmHTEGSpqYfxxKB4a+JY6VzZdL9e65P7YxqfL9Ag@mail.gmail.com \
--to=drake@endlessm.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jonathan.derrick@intel.com \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sai.praneeth.prakhya@intel.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).