From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH rc v3] iommufd/fault: Use a separate spinlock to protect fault->deliver list
Date: Mon, 20 Jan 2025 11:00:49 -0400 [thread overview]
Message-ID: <20250120150049.GJ5556@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB527693E6217946E1386B72038CE72@BN9PR11MB5276.namprd11.prod.outlook.com>
On Mon, Jan 20, 2025 at 09:22:28AM +0000, Tian, Kevin wrote:
> But I didn't see the similar logic in arm_smmu_attach_dev_blocked().
> And arm_smmu_evtq_thread() just removes an entry from the cmd
> queue and calls arm_smmu_handle_evt() to report. Seems no track of
> when those events are delivered.
I did not look closely, but I would not be surprised if this is the
case.
Jason
prev parent reply other threads:[~2025-01-20 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 2:04 [PATCH rc v3] iommufd/fault: Use a separate spinlock to protect fault->deliver list Nicolin Chen
2025-01-17 6:20 ` Tian, Kevin
2025-01-17 14:38 ` Jason Gunthorpe
2025-01-17 18:48 ` Nicolin Chen
2025-01-20 9:22 ` Tian, Kevin
2025-01-20 15:00 ` Jason Gunthorpe [this message]
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=20250120150049.GJ5556@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.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