From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: ashok.raj@intel.com, jacob.jun.pan@linux.intel.com,
kevin.tian@intel.com,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Daniel Drake <drake@endlessm.com>,
Derrick Jonathan <jonathan.derrick@intel.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v3 0/3] Replace private domain with per-group default domain
Date: Thu, 16 Apr 2020 14:23:51 +0800 [thread overview]
Message-ID: <20200416062354.10307-1-baolu.lu@linux.intel.com> (raw)
Some devices are required to use a specific type (identity or dma)
of default domain when they are used with a vendor iommu. When the
system level default domain type is different from it, the vendor
iommu driver has to request a new default domain with either
iommu_request_dma_domain_for_dev() or iommu_request_dm_for_dev()
in the add_dev() callback. Unfortunately, these two helpers only
work when the group hasn't been assigned to any other devices,
hence, some vendor iommu driver has to use a private domain if
it fails to request a new default one.
Joerg proposed an on-going proposal which makes the default domain
framework to support configuring per-group default domain during
boot process.
https://lkml.org/lkml/2020/4/14/616
Hence, there is no need to keep the private domain implementation
in the Intel IOMMU driver. This patch series aims to remove it.
Best regards,
baolu
Change log:
v2->v3:
- Port necessary patches on the top of Joerg's new proposal.
https://lkml.org/lkml/2020/4/14/616
The per-group default domain proposed previously in this series
will be deprecated due to a race concern between domain switching
and device driver probing.
v1->v2:
- Rename the iommu ops callback to def_domain_type
Lu Baolu (3):
iommu/vt-d: Allow 32bit devices to uses DMA domain
iommu/vt-d: Allow PCI sub-hierarchy to use DMA domain
iommu/vt-d: Apply per-device dma_ops
drivers/iommu/intel-iommu.c | 396 +++---------------------------------
1 file changed, 26 insertions(+), 370 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-16 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 6:23 Lu Baolu [this message]
2020-04-16 6:23 ` [PATCH v3 1/3] iommu/vt-d: Allow 32bit devices to uses DMA domain Lu Baolu
2020-04-16 7:01 ` Christoph Hellwig
2020-04-16 7:40 ` Lu Baolu
2020-04-17 6:50 ` Christoph Hellwig
2020-04-17 12:49 ` Lu Baolu
2020-04-16 6:23 ` [PATCH v3 2/3] iommu/vt-d: Allow PCI sub-hierarchy to use " Lu Baolu
2020-04-16 6:23 ` [PATCH v3 3/3] iommu/vt-d: Apply per-device dma_ops Lu Baolu
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=20200416062354.10307-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=drake@endlessm.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
Powered by JetHome