From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: [RFC] iommufd: Use accurate dev_id in the PRI forwarding path
Date: Thu, 6 Mar 2025 12:55:57 +0800 [thread overview]
Message-ID: <90bc8ef7-3e53-4d02-b1bc-2db7f6943429@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB52760A7D6D2A5680A3DC240C8CCA2@BN9PR11MB5276.namprd11.prod.outlook.com>
On 3/6/25 12:10, Tian, Kevin wrote:
>> From: Liu, Yi L <yi.l.liu@intel.com>
>> Sent: Thursday, March 6, 2025 11:30 AM
>>
>> On 2025/3/6 11:10, Tian, Kevin wrote:
>>>> From: Jason Gunthorpe <jgg@nvidia.com>
>>>> Sent: Thursday, March 6, 2025 1:19 AM
>>>>
>>>> I'm confused about how that can even work if the RID is erased in the
>>>> fabric, how do we deliver the PRI response to the correct entity?
>>>>
>>
>> If the RID is detached, kernel should response any pending PRIs. If user
>> sends a response, it won't suit any pending PRI then dropped.
>>
>
> Jason talked about the case where the iommu group is created e.g
> for a legacy PCI bridge, with all devices behind sharing a same RID.
> Then there is no way to know which device should receive the response.
The PCI spec requires,
"It (ATS) is permitted to be implemented by Endpoints or RCiEPs."
... but DMA aliases could also be created by pci_add_dma_alias().
Thanks,
baolu
next prev parent reply other threads:[~2025-03-06 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:03 [RFC] iommufd: Use accurate dev_id in the PRI forwarding path Yi Liu
2025-03-05 17:18 ` Jason Gunthorpe
2025-03-06 3:10 ` Tian, Kevin
2025-03-06 3:19 ` Baolu Lu
2025-03-06 3:30 ` Yi Liu
2025-03-06 4:10 ` Tian, Kevin
2025-03-06 4:55 ` Baolu Lu [this message]
2025-03-06 5:01 ` Yi Liu
2025-03-06 12:13 ` Jason Gunthorpe
2025-03-06 7:09 ` Yi Liu
2025-03-06 19:06 ` Jason Gunthorpe
2025-03-07 1:32 ` 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=90bc8ef7-3e53-4d02-b1bc-2db7f6943429@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.