[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241017130805.GA926121@ziepe.ca>
Date: Thu, 17 Oct 2024 10:08:05 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Zhangfei Gao <zhangfei.gao@...aro.org>,
Lu Baolu <baolu.lu@...ux.intel.com>
Cc: Kevin Tian <kevin.tian@...el.com>, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Nicolin Chen <nicolinc@...dia.com>, Yi Liu <yi.l.liu@...el.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Joel Granados <j.granados@...sung.com>, iommu@...ts.linux.dev,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com>
Subject: Re: [PATCH v8 07/10] iommufd: Fault-capable hwpt
attach/detach/replace
On Thu, Oct 17, 2024 at 08:35:24PM +0800, Zhangfei Gao wrote:
> Yes, you are right
> I am using SRIOV vf and stall feature, so is_virtfn == true
>
> Our ACC devices are fake pci endpoint devices which supports stall,
> And they also supports sriov
>
> So I have to ignore the limitation.
I see, so that is more complicated.
Lu, what do you think about also checking if the PCI function has PRI
? If not PRI assume the fault is special and doesn't follow PRI rules?
Or maybe we can have the iommu driver tag the event as a PRI/not-PRI
fault?
Jason
Powered by blists - more mailing lists