From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: <linux-kernel@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Mostafa Saleh <smostafa@google.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Robin Murphy <robin.murphy@arm.com>,
Zhang Yu <zhangyu1@linux.microsoft.com>,
Jean Philippe-Brucker <jean-philippe@linaro.org>,
Alexander Grest <Alexander.Grest@microsoft.com>
Subject: Re: [PATCH v3 1/2] iommu/arm-smmu-v3: Fix CMDQ timeout warning
Date: Wed, 5 Nov 2025 13:22:01 -0800 [thread overview]
Message-ID: <20251105132201.00004a5d@linux.microsoft.com> (raw)
In-Reply-To: <aQupGR8QsS2h7xY/@Asurada-Nvidia>
Hi Nicolin,
On Wed, 5 Nov 2025 11:44:25 -0800
Nicolin Chen <nicolinc@nvidia.com> wrote:
> On Wed, Nov 05, 2025 at 11:06:37AM -0800, Jacob Pan wrote:
> > + ret = queue_poll(qp);
> > + if (ret == -ETIMEDOUT) {
> > + dev_err_ratelimited(smmu->dev, "CMDQ timed out,
> > cons: %08x, prod: 0x%08x\n",
> > + llq->cons, llq->prod);
> > + /* Restart the timer */
> > + queue_poll_init(smmu, qp);
> > + } else if (ret) {
> > + dev_err_ratelimited(smmu->dev, "CMDQ poll error
> > %d\n", ret);
>
> I don't think you need this "if (ret)", as queue_poll() returns
> either 0 or -ETIMEOUT. And the patch that I shared with you has
> this noted clearly.
I agree it is not needed for now. But in general it is more robust not
to assume return value never changes.
I can delete that.
Thanks,
Jacob
next prev parent reply other threads:[~2025-11-05 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 19:06 [PATCH v3 0/2] SMMU v3 CMDQ fix and improvement Jacob Pan
2025-11-05 19:06 ` [PATCH v3 1/2] iommu/arm-smmu-v3: Fix CMDQ timeout warning Jacob Pan
2025-11-05 19:44 ` Nicolin Chen
2025-11-05 21:22 ` Jacob Pan [this message]
2025-11-05 19:06 ` [PATCH v3 2/2] iommu/arm-smmu-v3: Improve CMDQ lock fairness and efficiency Jacob Pan
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=20251105132201.00004a5d@linux.microsoft.com \
--to=jacob.pan@linux.microsoft.com \
--cc=Alexander.Grest@microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.com \
--cc=will@kernel.org \
--cc=zhangyu1@linux.microsoft.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.