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: Wed, 16 Nov 2022 13:20:07 +0800 [thread overview]
Message-ID: <40f5a81b-c40e-27e9-bc71-421f80792a79@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>
Patch queued for v6.1. Thank you!
https://lore.kernel.org/linux-iommu/20221116051544.26540-1-baolu.lu@linux.intel.com/
Best regards,
baolu
prev parent reply other threads:[~2022-11-16 5:27 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
2022-11-16 5:20 ` Baolu Lu [this message]
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=40f5a81b-c40e-27e9-bc71-421f80792a79@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