From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yi Liu <yi.l.liu@intel.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Unconditionally flush device TLB for pasid table updates
Date: Tue, 20 Aug 2024 15:37:07 +0800 [thread overview]
Message-ID: <f9ee4657-eea5-4a82-8e01-0396948ed755@linux.intel.com> (raw)
In-Reply-To: <9047e540-a993-473c-9d24-8359cec67b5b@intel.com>
On 2024/8/20 15:09, Yi Liu wrote:
> On 2024/8/20 11:02, Lu Baolu wrote:
>> The caching mode of an IOMMU is irrelevant to the behavior of the device
>> TLB. Previously, commit <304b3bde24b5> ("iommu/vt-d: Remove caching mode
>> check before device TLB flush") removed this redundant check in the
>> domain unmap path.
>>
>> Checking the caching mode before flushing the device TLB after a pasid
>> table entry is updated is unnecessary and can lead to inconsistent
>> behavior.
>>
>> Extends this consistency by removing the caching mode check in the pasid
>> table update path.
>
> I'm wondering if a fix tag is needed here. Before this patch, the guest
> kernel does not issue device TLB invalidation. This may be a problem for
> the emulated devices that support ATS capability. The cache in device
> side would be stale. Although some vIOMMU like QEMU virtual VT-d would
> notify the emulated devices to flush their cache when handling the unmap
> event. [1]. But this is not required by VT-d spec. So it's possible that
> other vIOMMU may not do it. So this patch appears to fix an issue, so a fix
> tag may be necessary. How about your thought?
It depends on whether this solves any real or potential issues.
Thanks,
baolu
next prev parent reply other threads:[~2024-08-20 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 3:02 [PATCH 1/1] iommu/vt-d: Unconditionally flush device TLB for pasid table updates Lu Baolu
2024-08-20 7:09 ` Yi Liu
2024-08-20 7:37 ` Baolu Lu [this message]
2024-08-21 7:54 ` Yi Liu
2024-09-02 2:38 ` 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=f9ee4657-eea5-4a82-8e01-0396948ed755@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@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