From: Baolu Lu <baolu.lu@linux.intel.com>
To: Dmytro Maluka <dmaluka@chromium.org>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux.dev
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
"Vineeth Pillai (Google)" <vineeth@bitbyteword.org>,
Aashish Sharma <aashish@aashishsharma.net>,
Grzegorz Jaszczyk <jaszczyk@chromium.org>,
Chuanxiao Dong <chuanxiao.dong@intel.com>,
Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH v2] iommu/vt-d: Flush cache for PASID table before using it
Date: Tue, 20 Jan 2026 15:01:43 +0800 [thread overview]
Message-ID: <69866166-32ce-48a7-9429-c6b77afa6eb0@linux.intel.com> (raw)
In-Reply-To: <20251221123508.37495-1-dmaluka@chromium.org>
On 12/21/25 20:35, Dmytro Maluka wrote:
> When writing the address of a freshly allocated zero-initialized PASID
> table to a PASID directory entry, do that after the CPU cache flush for
> this PASID table, not before it, to avoid the time window when this
> PASID table may be already used by non-coherent IOMMU hardware while
> its contents in RAM is still some random old data, not zero-initialized.
>
> v1 -> v2:
> Add Fixes: tag.
>
> Fixes: 194b3348bdbb ("iommu/vt-d: Fix PASID directory pointer coherency")
> Signed-off-by: Dmytro Maluka<dmaluka@chromium.org>
> ---
> drivers/iommu/intel/pasid.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Queued for iommu next.
Thanks,
baolu
prev parent reply other threads:[~2026-01-20 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 12:35 [PATCH v2] iommu/vt-d: Flush cache for PASID table before using it Dmytro Maluka
2026-01-06 7:51 ` Tian, Kevin
2026-01-20 7:01 ` 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=69866166-32ce-48a7-9429-c6b77afa6eb0@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=aashish@aashishsharma.net \
--cc=chuanxiao.dong@intel.com \
--cc=dmaluka@chromium.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jaszczyk@chromium.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vineeth@bitbyteword.org \
--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