Linux IOMMU Development
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Tina Zhang <tina.zhang@intel.com>, iommu@lists.linux.dev
Cc: baolu.lu@linux.intel.com
Subject: Re: [PATCH] iommu/vt-d: Present Access bit for IOVA in FL non-leaf paging entries
Date: Mon, 14 Nov 2022 10:26:21 +0800	[thread overview]
Message-ID: <ca467b3b-cf4a-caea-99eb-9d9f47819c98@linux.intel.com> (raw)
In-Reply-To: <20221113010324.1094483-1-tina.zhang@intel.com>

On 11/13/22 9:03 AM, Tina Zhang wrote:
> The A/D bits are presented for IOVA over first level(FL) usage for both
> kernel DMA (i.e, domain typs is IOMMU_DOMAIN_DMA) and user space DMA
> usage (i.e., domain type is IOMMU_DOMAIN_UNMANAGED).
> 
> Preseting A bit in FL requires to present the bit in very related paging
> entries, including the non-leaf ones. Otherwise, DMA fault may come out.
> For example, in a case of ECAP_REG.SMPWC==0, the DMA fault would be
> "SM: A/D bit update needed in first-level entry when set up in no
> snoop".
> 
> Signed-off-by: Tina Zhang <tina.zhang@intel.com>

Thanks for this patch.

Fixes: 289b3b005cb9 ("iommu/vt-d: Preset A/D bits for user space DMA usage")

Best regards,
baolu

> ---
>   drivers/iommu/intel/iommu.c | 8 +++-----
>   1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index 48cdcd0a5cf3..996a8b5ee5ee 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -959,11 +959,9 @@ static struct dma_pte *pfn_to_dma_pte(struct dmar_domain *domain,
>   
>   			domain_flush_cache(domain, tmp_page, VTD_PAGE_SIZE);
>   			pteval = ((uint64_t)virt_to_dma_pfn(tmp_page) << VTD_PAGE_SHIFT) | DMA_PTE_READ | DMA_PTE_WRITE;
> -			if (domain_use_first_level(domain)) {
> -				pteval |= DMA_FL_PTE_XD | DMA_FL_PTE_US;
> -				if (iommu_is_dma_domain(&domain->domain))
> -					pteval |= DMA_FL_PTE_ACCESS;
> -			}
> +			if (domain_use_first_level(domain))
> +				pteval |= DMA_FL_PTE_XD | DMA_FL_PTE_US | DMA_FL_PTE_ACCESS;
> +
>   			if (cmpxchg64(&pte->val, 0ULL, pteval))
>   				/* Someone else set it while we were thinking; use theirs. */
>   				free_pgtable_page(tmp_page);

  reply	other threads:[~2022-11-14  2:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13  1:03 [PATCH] iommu/vt-d: Present Access bit for IOVA in FL non-leaf paging entries Tina Zhang
2022-11-14  2:26 ` Baolu Lu [this message]
2022-11-16  5:20 ` Baolu Lu

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=ca467b3b-cf4a-caea-99eb-9d9f47819c98@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=tina.zhang@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