linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	jsnitsel@redhat.com, praan@google.com,
	linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu-v3: Allow stream table to have nodes with the same ID
Date: Fri, 11 Apr 2025 08:45:36 -0300	[thread overview]
Message-ID: <20250411114536.GB8423@nvidia.com> (raw)
In-Reply-To: <20250411044706.356395-1-nicolinc@nvidia.com>

On Thu, Apr 10, 2025 at 09:47:06PM -0700, Nicolin Chen wrote:
> Change the arm_smmu_streams_cmp_node() to allow the stream table to hold
> multiple nodes with the same Stream ID. Meanwhile, the reverse lookup from
> the Stream ID to a device pointer will have to be broken, i.e. the eventq
> handler will no longer find the device with a Stream ID in such cases.
> 
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> ---
>  drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 31 +++++++++++++++++++--
>  1 file changed, 29 insertions(+), 2 deletions(-)

This should go to rc, also a fixes line is probably something like:

Fixes: cdf315f907d4 ("iommu/arm-smmu-v3: Maintain a SID->device structure")

Since it has been broken for a while, it just didn't become critical
until probe started failing in v6.15-rc1

Jason


  reply	other threads:[~2025-04-11 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  4:47 [PATCH] iommu/arm-smmu-v3: Allow stream table to have nodes with the same ID Nicolin Chen
2025-04-11 11:45 ` Jason Gunthorpe [this message]
2025-04-11 12:10 ` Robin Murphy
2025-04-11 13:01   ` Jason Gunthorpe
2025-04-11 13:35     ` Pranjal Shrivastava
2025-04-11 13:42       ` Jason Gunthorpe
2025-04-11 15:13 ` Robin Murphy
2025-04-11 23:33   ` Nicolin Chen
2025-04-11 23:44     ` Jason Gunthorpe
2025-04-12  0:07       ` Nicolin Chen
2025-04-12  3:39         ` Nicolin Chen
2025-04-12 13:55           ` Jason Gunthorpe
2025-04-12 17:03             ` Nicolin Chen

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=20250411114536.GB8423@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).