From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: Ankit Soni <Ankit.Soni@amd.com>
Cc: <iommu@lists.linux.dev>, <vasant.hegde@amd.com>,
<suravee.suthikulpanit@amd.com>, <joro@8bytes.org>,
<will@kernel.org>, <robin.murphy@arm.com>,
<linux-kernel@vger.kernel.org>, <Srikanth.Aithal@amd.com>
Subject: Re: [PATCH] iommu/amd: serialize sequence allocation under concurrent TLB invalidations
Date: Tue, 20 Jan 2026 09:24:27 -0800 [thread overview]
Message-ID: <20260120092427.00001794@linux.microsoft.com> (raw)
In-Reply-To: <abcfda19c05becb988ede3a1a0ba6d87161943bf.1768899638.git.Ankit.Soni@amd.com>
Hi Ankit,
On Tue, 20 Jan 2026 09:05:07 +0000
Ankit Soni <Ankit.Soni@amd.com> wrote:
> With concurrent TLB invalidations, completion wait randomly gets
> timed out because cmd_sem_val was incremented outside the IOMMU
> spinlock, allowing CMD_COMPL_WAIT commands to be queued out of
> sequence and breaking the ordering assumption in wait_on_sem().
> Move the cmd_sem_val increment under iommu->lock so completion
> sequence allocation is serialized with command queuing.
> And remove the unnecessary return.
>
> Fixes: d2a0cac10597 ("iommu/amd: move wait_on_sem() out of spinlock")
>
> Tested-by: Srikanth Aithal <sraithal@amd.com>
> Reported-by: Srikanth Aithal <sraithal@amd.com>
> Signed-off-by: Ankit Soni <Ankit.Soni@amd.com>
> ---
> drivers/iommu/amd/iommu.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index d7f457338de7..593fb879b7b0 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -1422,6 +1422,12 @@ static int iommu_queue_command(struct
> amd_iommu *iommu, struct iommu_cmd *cmd) return
> iommu_queue_command_sync(iommu, cmd, true); }
>
> +static u64 get_cmdsem_val(struct amd_iommu *iommu)
> +{
> + lockdep_assert_held(&iommu->lock);
> + return atomic64_inc_return(&iommu->cmd_sem_val);
Do we still need this to be atomic now that it’s protected by a
spinlock?
> +}
> +
> /*
> * This function queues a completion wait command into the command
> * buffer of an IOMMU
> @@ -1436,11 +1442,11 @@ static int iommu_completion_wait(struct
> amd_iommu *iommu) if (!iommu->need_sync)
> return 0;
>
> - data = atomic64_inc_return(&iommu->cmd_sem_val);
> - build_completion_wait(&cmd, iommu, data);
> -
> raw_spin_lock_irqsave(&iommu->lock, flags);
>
> + data = get_cmdsem_val(iommu);
> + build_completion_wait(&cmd, iommu, data);
> +
> ret = __iommu_queue_command_sync(iommu, &cmd, false);
> raw_spin_unlock_irqrestore(&iommu->lock, flags);
>
> @@ -3119,10 +3125,11 @@ static void
> iommu_flush_irt_and_complete(struct amd_iommu *iommu, u16 devid)
> return;
> build_inv_irt(&cmd, devid);
> - data = atomic64_inc_return(&iommu->cmd_sem_val);
> - build_completion_wait(&cmd2, iommu, data);
>
> raw_spin_lock_irqsave(&iommu->lock, flags);
> + data = get_cmdsem_val(iommu);
> + build_completion_wait(&cmd2, iommu, data);
> +
> ret = __iommu_queue_command_sync(iommu, &cmd, true);
> if (ret)
> goto out_err;
> @@ -3136,7 +3143,6 @@ static void iommu_flush_irt_and_complete(struct
> amd_iommu *iommu, u16 devid)
> out_err:
> raw_spin_unlock_irqrestore(&iommu->lock, flags);
> - return;
> }
>
> static inline u8 iommu_get_int_tablen(struct iommu_dev_data
> *dev_data)
next prev parent reply other threads:[~2026-01-20 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:05 [PATCH] iommu/amd: serialize sequence allocation under concurrent TLB invalidations Ankit Soni
2026-01-20 17:24 ` Jacob Pan [this message]
2026-01-21 6:49 ` Ankit Soni
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=20260120092427.00001794@linux.microsoft.com \
--to=jacob.pan@linux.microsoft.com \
--cc=Ankit.Soni@amd.com \
--cc=Srikanth.Aithal@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=vasant.hegde@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 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.