Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Kevin Tian <kevin.tian@intel.com>,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/7] iommu/vt-d: Add support for static identity domain
Date: Tue, 6 Aug 2024 14:18:54 -0300	[thread overview]
Message-ID: <20240806171854.GO676757@ziepe.ca> (raw)
In-Reply-To: <20240806023941.93454-7-baolu.lu@linux.intel.com>

On Tue, Aug 06, 2024 at 10:39:40AM +0800, Lu Baolu wrote:
> Software determines VT-d hardware support for passthrough translation by
> inspecting the capability register. If passthrough translation is not
> supported, the device is instructed to use DMA domain for its default
> domain.
> 
> Add a global static identity domain with guaranteed attach semantics for
> IOMMUs that support passthrough translation mode.
> 
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
>  drivers/iommu/intel/iommu.c | 102 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 102 insertions(+)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

> +static int identity_domain_attach_dev(struct iommu_domain *domain, struct device *dev)
> +{
> +	struct device_domain_info *info = dev_iommu_priv_get(dev);
> +	struct intel_iommu *iommu = info->iommu;
> +	int ret;
> +
> +	device_block_translation(dev);

Though it would be nice if this wasn't hitfull like this, someday..

Jason

  reply	other threads:[~2024-08-06 17:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  2:39 [PATCH v3 0/7] iommu/vt-d: Convert to use static identity domain Lu Baolu
2024-08-06  2:39 ` [PATCH v3 1/7] iommu/vt-d: Require DMA domain if hardware not support passthrough Lu Baolu
2024-08-06 16:54   ` Jason Gunthorpe
2024-08-14 16:13   ` Jerry Snitselaar
2024-08-06  2:39 ` [PATCH v3 2/7] iommu/vt-d: Remove identity mappings from si_domain Lu Baolu
2024-08-06 17:05   ` Jason Gunthorpe
2024-08-07  6:14     ` Baolu Lu
2024-08-06  2:39 ` [PATCH v3 3/7] iommu/vt-d: Always reserve a domain ID for identity setup Lu Baolu
2024-08-06 17:06   ` Jason Gunthorpe
2024-08-07  6:19     ` Baolu Lu
2024-08-07 12:09       ` Jason Gunthorpe
2024-08-07 13:38         ` Baolu Lu
2024-08-14 16:31   ` Jerry Snitselaar
2024-08-06  2:39 ` [PATCH v3 4/7] iommu/vt-d: Prepare for global static identity domain Lu Baolu
2024-08-06 17:12   ` Jason Gunthorpe
2024-08-07  6:41     ` Baolu Lu
2024-08-07 12:17       ` Jason Gunthorpe
2024-08-07 13:44         ` Baolu Lu
2024-08-06  2:39 ` [PATCH v3 5/7] iommu/vt-d: Factor out helpers from domain_context_mapping_one() Lu Baolu
2024-08-06 17:13   ` Jason Gunthorpe
2024-08-14 16:19   ` Jerry Snitselaar
2024-08-06  2:39 ` [PATCH v3 6/7] iommu/vt-d: Add support for static identity domain Lu Baolu
2024-08-06 17:18   ` Jason Gunthorpe [this message]
2024-08-06  2:39 ` [PATCH v3 7/7] iommu/vt-d: Cleanup si_domain Lu Baolu
2024-08-06 17:19   ` Jason Gunthorpe

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=20240806171854.GO676757@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    /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