From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>, Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
jean-philippe <jean-philippe@linaro.org>,
shamiali2008@gmail.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommufd: modify iommufd_fault_iopf_enable limitation
Date: Thu, 7 Nov 2024 09:51:11 +0800 [thread overview]
Message-ID: <fcef9cb1-797a-496a-9ef5-1e2f530dc8f6@linux.intel.com> (raw)
In-Reply-To: <20241106135944.GP458827@nvidia.com>
On 11/6/24 21:59, Jason Gunthorpe wrote:
> On Wed, Nov 06, 2024 at 05:47:09AM +0000, Zhangfei Gao wrote:
>> On Mon, 28 Oct 2024 at 11:32, Zhangfei Gao<zhangfei.gao@linaro.org> wrote:
>>> iommufd_fault_iopf_enable has limitation to PRI on PCI/SRIOV VFs
>>> because the PRI might be a shared resource and current iommu
>>> subsystem is not ready to support enabling/disabling PRI on a VF
>>> without any impact on others.
>>>
>>> However, we have devices that appear as PCI but are actually on the
>>> AMBA bus. These fake PCI devices have PASID capability, support
>>> stall as well as SRIOV, so remove the limitation for these devices.
>>>
>>> Signed-off-by: Zhangfei Gao<zhangfei.gao@linaro.org>
>>> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
>>> ---
>>> drivers/iommu/iommufd/fault.c | 9 +++++++--
>>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/iommu/iommufd/fault.c b/drivers/iommu/iommufd/fault.c
>>> index bca956d496bd..8b3e34250dae 100644
>>> --- a/drivers/iommu/iommufd/fault.c
>>> +++ b/drivers/iommu/iommufd/fault.c
>>> @@ -10,6 +10,7 @@
>>> #include <linux/module.h>
>>> #include <linux/mutex.h>
>>> #include <linux/pci.h>
>>> +#include <linux/pci-ats.h>
>>> #include <linux/poll.h>
>>> #include <uapi/linux/iommufd.h>
>>>
>>> @@ -27,8 +28,12 @@ static int iommufd_fault_iopf_enable(struct iommufd_device *idev)
>>> * resource between PF and VFs. There is no coordination for this
>>> * shared capability. This waits for a vPRI reset to recover.
>>> */
>>> - if (dev_is_pci(dev) && to_pci_dev(dev)->is_virtfn)
>>> - return -EINVAL;
>>> + if (dev_is_pci(dev)) {
>>> + struct pci_dev *pdev = to_pci_dev(dev);
>>> +
>>> + if (pdev->is_virtfn && pci_pri_supported(pdev))
>>> + return -EINVAL;
>>> + }
>>>
>>> mutex_lock(&idev->iopf_lock);
>>> /* Device iopf has already been on. */
>>>
>> Hi, Jason
>>
>> Would you mind also taking a look at this.
> Lu? Are you OK with this?
This change looks good to me. But the s-o-b chain would make more sense
if we can make it like this,
Co-developed-by: Lu Baolu <baolu.lu@linux.intel.com>
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
Signed-off-by: Zhangfei Gao<zhangfei.gao@linaro.org>
With this addressed,
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
--
baolu
next prev parent reply other threads:[~2024-11-07 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 11:32 [PATCH] iommufd: modify iommufd_fault_iopf_enable limitation Zhangfei Gao
2024-11-06 5:47 ` Zhangfei Gao
2024-11-06 13:59 ` Jason Gunthorpe
2024-11-07 1:51 ` Baolu Lu [this message]
2024-11-07 4:40 ` Zhangfei Gao
2024-11-07 4:37 ` [PATCH v2] " Zhangfei Gao
2024-11-07 17:12 ` Jason Gunthorpe
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=fcef9cb1-797a-496a-9ef5-1e2f530dc8f6@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shamiali2008@gmail.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@linaro.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