All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/3] iommu/amd: make iommu_completion_wait() wait for flushes queued by other CPUs
Date: Thu, 12 Nov 2026 13:40:50 +0100	[thread overview]
Message-ID: <179448725082.4060562.14810298746628558988.b4-ty@b4> (raw)
In-Reply-To: <20261110191836.3000352-1-den@openvz.org>

On Tue, 10 Nov 2026 20:18:33 +0100, Denis V. Lunev wrote:
> iommu/amd: make iommu_completion_wait() wait for flushes queued by other CPUs
> 
> iommu_completion_wait() checks iommu->need_sync without iommu->lock and
> returns at once when it is clear. A completion wait queued by another
> CPU clears the flag before the IOMMU has executed the commands in front
> of it, so the caller can return while its own invalidations are still
> pending. After an unmap that lets an IOVA or a page table page be
> reused while the IOMMU may still hold the old translation. It also
> leaves a hole in "iommu/amd/pgtbl: fix DMA faults on IOVAs mapped while
> the table grows": the DTE flush done before the new page table level is
> published can return before the IOMMU has dropped the old DTE.
> 
> [...]

Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.21.vz10, thanks!

[1/3] ms/iommu/amd: move wait_on_sem() out of spinlock
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/3e6384ffedcb
[2/3] ms/iommu/amd: serialize sequence allocation under concurrent TLB invalidations
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5a6596791b87
[3/3] ms/iommu/amd: Wait for completion instead of returning early in iommu_completion_wait()
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/516fe340b0d5

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team


_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-12 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 19:18 Denis V. Lunev
2026-11-10 19:18 ` [Devel] [PATCH hci-8.1 1/3] ms/iommu/amd: move wait_on_sem() out of spinlock Denis V. Lunev
2026-11-10 19:23   ` no-reply
2026-11-10 19:18 ` [Devel] [PATCH hci-8.1 2/3] ms/iommu/amd: serialize sequence allocation under concurrent TLB invalidations Denis V. Lunev
2026-11-10 19:22   ` no-reply
2026-11-10 19:18 ` [Devel] [PATCH hci-8.1 3/3] ms/iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() Denis V. Lunev
2026-11-10 19:24   ` no-reply
2026-11-12 12:40 ` Konstantin Khorenko [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=179448725082.4060562.14810298746628558988.b4-ty@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=devel@openvz.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.