From: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: <will@kernel.org>, <robin.murphy@arm.com>,
<iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<suravee.suthikulpanit@amd.com>, <Vasant.Hegde@amd.com>,
<Santosh.Shukla@amd.com>
Subject: Re: [PATCH] iommu/amd: Enhance "Completion-wait Time-out" error message
Date: Wed, 5 Nov 2025 12:13:48 +0530 [thread overview]
Message-ID: <eb0624df-3cae-46ec-9f7e-b45bea46a345@amd.com> (raw)
In-Reply-To: <tgugv7ebuxtnp6ou5jnt7od7jmccsipblqityiinhkgratosu6@bxsr73hpiiny>
Hey Joerg,
On 10/27/2025 6:19 PM, Jörg Rödel wrote:
> Hey Dheeraj,
>
> On Thu, Oct 16, 2025 at 08:38:09PM +0530, Dheeraj Kumar Srivastava wrote:
>> static int wait_on_sem(struct amd_iommu *iommu, u64 data)
>> {
>> - int i = 0;
>> + struct iommu_cmd *cmd;
>> + int i = 0, j;
>>
>> while (*iommu->cmd_sem != data && i < LOOP_TIMEOUT) {
>> udelay(1);
>> @@ -1166,7 +1167,33 @@ static int wait_on_sem(struct amd_iommu *iommu, u64 data)
>> }
>>
>> if (i == LOOP_TIMEOUT) {
>> - pr_alert("Completion-Wait loop timed out\n");
>> + int head, tail;
>> +
>> + head = readl(iommu->mmio_base + MMIO_CMD_HEAD_OFFSET);
>> + tail = readl(iommu->mmio_base + MMIO_CMD_TAIL_OFFSET);
>> +
>> + pr_alert("IOMMU %04x:%02x:%02x.%01x: Completion-Wait loop timed out\n",
>> + iommu->pci_seg->id, PCI_BUS_NUM(iommu->devid),
>> + PCI_SLOT(iommu->devid), PCI_FUNC(iommu->devid));
>
> Better use dev_err(&amd_iommu->dev->dev, ...) here.
In the early boot process, the command buffer is used but
iommu->dev->dev is not set, which can lead to a kernel crash with dev_err.
Thanks
Dheeraj
>
>> + if (!amd_iommu_dump) {
>> + /*
>> + * On command buffer completion timeout, step back by 2 commands
>> + * to locate the actual command that is causing the issue.
>> + */
>> + tail = (MMIO_CMD_BUFFER_TAIL(tail) - 2) & (CMD_BUFFER_ENTRIES - 1);
>> + cmd = (struct iommu_cmd *)(iommu->cmd_buf + tail * sizeof(*cmd));
>> + dump_command(iommu_virt_to_phys(cmd));
>> + } else {
>> + /* Dump entire command buffer along with head and tail indices */
>> + pr_alert("CMD Buffer head=%d tail=%d\n", (int)(MMIO_CMD_BUFFER_HEAD(head)),
>> + (int)(MMIO_CMD_BUFFER_TAIL(tail)));
>> + for (j = 0; j < CMD_BUFFER_ENTRIES; j++) {
>> + cmd = (struct iommu_cmd *)(iommu->cmd_buf + j * sizeof(*cmd));
>> + pr_err("%3d: %08x %08x %08x %08x\n", j, cmd->data[0], cmd->data[1],
>> + cmd->data[2], cmd->data[3]);
>> + }
>> + }
>
> I don't think it makes much sense to just print the command before the failed
> completion wait. In case of a timeout and amd_iommu_dump == true, just dump the
> whole pending command buffer, from head to tail.
>
> Also, please put all the parsing/dumping code into a separate function.
>
> Regards,
>
> Joerg
prev parent reply other threads:[~2025-11-05 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 15:08 Dheeraj Kumar Srivastava
2025-10-27 12:49 ` Jörg Rödel
2025-10-28 9:15 ` Vasant Hegde
2025-10-29 8:30 ` Jörg Rödel
2025-10-29 10:48 ` Vasant Hegde
2025-10-29 11:16 ` Dheeraj Kumar Srivastava
2025-11-05 6:43 ` Dheeraj Kumar Srivastava [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=eb0624df-3cae-46ec-9f7e-b45bea46a345@amd.com \
--to=dheerajkumar.srivastava@amd.com \
--cc=Santosh.Shukla@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.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
all inboxes | Powered by JetHome®