[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b64c5b16-79bd-182d-354b-73a74430a8cc@linux.intel.com>
Date: Mon, 5 Dec 2022 18:59:19 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc: baolu.lu@...ux.intel.com, LKML <linux-kernel@...r.kernel.org>,
iommu@...ts.linux.dev, Robin Murphy <robin.murphy@....com>,
Will Deacon <will@...nel.org>,
David Woodhouse <dwmw2@...radead.org>,
Raj Ashok <ashok.raj@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>, Yi Liu <yi.l.liu@...el.com>,
Yuzhang Luo <yuzhang.luo@...el.com>
Subject: Re: [PATCH v3] iommu/vt-d: Add a fix for devices need extra dtlb
flush
On 2022/12/5 18:43, Joerg Roedel wrote:
> On Tue, Nov 29, 2022 at 10:24:49PM -0800, Jacob Pan wrote:
>> drivers/iommu/intel/iommu.c | 67 +++++++++++++++++++++++++++++++++++--
>> drivers/iommu/intel/iommu.h | 3 ++
>> drivers/iommu/intel/svm.c | 5 ++-
>> 3 files changed, 72 insertions(+), 3 deletions(-)
> I removed this commit from my fixes branch. Please re-submit with the
> fix included and I will queue it for 6.2 once Lu Baolu acked it.
But this patch has already been merged in v6.1-rc7.
https://lore.kernel.org/linux-iommu/Y4oF8e7quzjm2kzD@8bytes.org/
Is this still feasible?
Best regards,
baolu
Powered by blists - more mailing lists