From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kevin.tian@intel.com, baolu.lu@linux.intel.com, iommu@lists.linux.dev
Subject: Re: [RFC] iommufd: Use accurate dev_id in the PRI forwarding path
Date: Wed, 5 Mar 2025 13:18:38 -0400 [thread overview]
Message-ID: <20250305171838.GC133783@nvidia.com> (raw)
In-Reply-To: <20250305130356.126424-1-yi.l.liu@intel.com>
On Wed, Mar 05, 2025 at 05:03:56AM -0800, Yi Liu wrote:
> Hi Jason, Kevin, Baolu,
>
> This is more a query, the patch here does not really work as there
> is locking issue. So I'd like to hear from you if any good idea.
>
> Detail as below:
>
> Existing code has a problem when the PRI happens on a device that has
> alias. The PRI reporting path uses the idev stored in the handle. While
> this idev is the first idev that attachs to the domain. If the PRI
> happens on devices other than the first attached device, then the idev
> stored in handle does not match.
Do you actually care about this? Can we say that devices that have
aliases do not allow PRI?
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?
Or do you mean something else by alias?
Jason
next prev parent reply other threads:[~2025-03-05 17:18 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 [this message]
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
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=20250305171838.GC133783@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--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.