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 v2 0/6] Replace private domain with per-group default domain Date: Sat, 14 Mar 2020 09:06:59 +0800 [thread overview] Message-ID: <20200314010705.30711-1-baolu.lu@linux.intel.com> (raw) Some devices are reqired 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. This patch series aims to remove the private domain requirement in vendor iommu driver with enabling the iommu generic code to support configuring per-group default domain. It introduces a new callback in iommu_ops, named def_domain_type(), so that the iommu generic code could check whether a device is required to use any specific type of default domain during the process of device probing. If unlikely a device requires a special default domain type other than that in use, iommu probe procedure will either allocate a new domain according to the specified domain type, or (if the group has other devices sitting in it) change the default domain. The vendor iommu driver which exposes the def_domain_type callback should guarantee that there're no multiple devices belonging to a same group require differnt types of default domain. Please help to review. Best regards, baolu Change log: v1->v2: - Rename the iommu ops callback to def_domain_type Lu Baolu (5): iommu: Configure default domain with def_domain_type iommu/vt-d: Don't force 32bit devices to uses DMA domain iommu/vt-d: Don't force PCI sub-hierarchy to use DMA domain iommu/vt-d: Add def_domain_type callback iommu/vt-d: Apply per-device dma_ops Sai Praneeth Prakhya (1): iommu: Add def_domain_type() callback in iommu_ops drivers/iommu/intel-iommu.c | 453 +++--------------------------------- drivers/iommu/iommu.c | 93 +++++++- include/linux/iommu.h | 6 + 3 files changed, 126 insertions(+), 426 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lu Baolu <baolu.lu@linux.intel.com> To: Joerg Roedel <joro@8bytes.org> Cc: kevin.tian@intel.com, ashok.raj@intel.com, linux-kernel@vger.kernel.org, Daniel Drake <drake@endlessm.com>, iommu@lists.linux-foundation.org, Robin Murphy <robin.murphy@arm.com>, Christoph Hellwig <hch@lst.de>, Derrick Jonathan <jonathan.derrick@intel.com> Subject: [PATCH v2 0/6] Replace private domain with per-group default domain Date: Sat, 14 Mar 2020 09:06:59 +0800 [thread overview] Message-ID: <20200314010705.30711-1-baolu.lu@linux.intel.com> (raw) Some devices are reqired 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. This patch series aims to remove the private domain requirement in vendor iommu driver with enabling the iommu generic code to support configuring per-group default domain. It introduces a new callback in iommu_ops, named def_domain_type(), so that the iommu generic code could check whether a device is required to use any specific type of default domain during the process of device probing. If unlikely a device requires a special default domain type other than that in use, iommu probe procedure will either allocate a new domain according to the specified domain type, or (if the group has other devices sitting in it) change the default domain. The vendor iommu driver which exposes the def_domain_type callback should guarantee that there're no multiple devices belonging to a same group require differnt types of default domain. Please help to review. Best regards, baolu Change log: v1->v2: - Rename the iommu ops callback to def_domain_type Lu Baolu (5): iommu: Configure default domain with def_domain_type iommu/vt-d: Don't force 32bit devices to uses DMA domain iommu/vt-d: Don't force PCI sub-hierarchy to use DMA domain iommu/vt-d: Add def_domain_type callback iommu/vt-d: Apply per-device dma_ops Sai Praneeth Prakhya (1): iommu: Add def_domain_type() callback in iommu_ops drivers/iommu/intel-iommu.c | 453 +++--------------------------------- drivers/iommu/iommu.c | 93 +++++++- include/linux/iommu.h | 6 + 3 files changed, 126 insertions(+), 426 deletions(-) -- 2.17.1 _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-03-14 1:09 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-14 1:06 Lu Baolu [this message] 2020-03-14 1:06 ` [PATCH v2 0/6] Replace private domain with per-group default domain Lu Baolu 2020-03-14 1:07 ` [PATCH v2 1/6] iommu: Add def_domain_type() callback in iommu_ops Lu Baolu 2020-03-14 1:07 ` Lu Baolu 2020-03-14 1:07 ` [PATCH v2 2/6] iommu: Configure default domain with def_domain_type Lu Baolu 2020-03-14 1:07 ` Lu Baolu 2020-03-19 14:03 ` Joerg Roedel 2020-03-19 14:03 ` Joerg Roedel 2020-03-20 9:06 ` Lu Baolu 2020-03-20 9:06 ` Lu Baolu 2020-03-14 1:07 ` [PATCH v2 3/6] iommu/vt-d: Don't force 32bit devices to uses DMA domain Lu Baolu 2020-03-14 1:07 ` Lu Baolu 2020-03-14 1:07 ` [PATCH v2 4/6] iommu/vt-d: Don't force PCI sub-hierarchy to use " Lu Baolu 2020-03-14 1:07 ` Lu Baolu 2020-03-14 1:07 ` [PATCH v2 5/6] iommu/vt-d: Add def_domain_type callback Lu Baolu 2020-03-14 1:07 ` Lu Baolu 2020-03-14 1:07 ` [PATCH v2 6/6] iommu/vt-d: Apply per-device dma_ops Lu Baolu 2020-03-14 1:07 ` 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=20200314010705.30711-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: linkBe 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.