From: Nicolin Chen <nicolinc@nvidia.com>
To: <joro@8bytes.org>, <kevin.tian@intel.com>, <jgg@nvidia.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>,
<baolu.lu@linux.intel.com>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <xueshuai@linux.alibaba.com>
Subject: Re: [PATCH rc v5] iommu: Fix nested pci_dev_reset_iommu_prepare/done()
Date: Sat, 4 Apr 2026 17:55:35 -0700 [thread overview]
Message-ID: <adGzB1qLGQqTJgi/@nvidia.com> (raw)
In-Reply-To: <20260404050243.141366-1-nicolinc@nvidia.com>
On Fri, Apr 03, 2026 at 10:02:43PM -0700, Nicolin Chen wrote:
> @@ -76,12 +76,28 @@ struct group_device {
> struct list_head list;
> struct device *dev;
> char *name;
> + bool blocked;
> + unsigned int reset_depth;
Perhaps I should have mentioned that this "blocked" will be useful
when shared with the followup series to flag the device blocked by
an ongoing/failed reset or quarantine.
Nicolin
next prev parent reply other threads:[~2026-04-05 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 5:02 [PATCH rc v5] iommu: Fix nested pci_dev_reset_iommu_prepare/done() Nicolin Chen
2026-04-05 0:55 ` Nicolin Chen [this message]
2026-04-07 6:36 ` Shuai Xue
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=adGzB1qLGQqTJgi/@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox