From: Jan Beulich <jbeulich@suse.com>
To: Teddy Astie <teddy.astie@vates.tech>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger@xenproject.org>,
"Jason Andryuk" <jason.andryuk@amd.com>,
xen-devel@lists.xenproject.org
Subject: Re: [RFC PATCH v7 05/14] iommu: Simplify quarantine logic
Date: Wed, 19 Aug 2026 17:21:54 +0200 [thread overview]
Message-ID: <1e6aa092-778f-4826-8013-aa527a4858eb@suse.com> (raw)
In-Reply-To: <31b2ede1eab92048b69fe4999a35eb7d4a4617ba.1763569135.git.teddy.astie@vates.tech>
On 20.11.2025 12:09, Teddy Astie wrote:
> Current quarantine code is very hard to change and is very
> complicated, remove most bits of it and replace it with direct
> reassignement to dom_io domain instead.
Well, again far too little of a description, even when taking ...
> Signed-off-by: Teddy Astie <teddy.astie@vates.tech>
> ---
> A idea would be to rework this feature using the new reworked
> IOMMU subsystem.
... this sentence into account: As I can't spot replacement of present logic
(fill_qpt() being a prime example) - how is existing behavior retained? I
can't help the impression that you simply lose functionality, which is not
an option.
Jan
next prev parent reply other threads:[~2026-08-19 15:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 11:09 [RFC PATCH v7 00/14] IOMMU subsystem redesign and PV-IOMMU interface Teddy Astie
2025-11-20 11:09 ` [RFC PATCH v7 02/14] docs/designs: Add a design document for PV-IOMMU Teddy Astie
2025-11-20 11:09 ` [RFC PATCH v7 01/14] docs/designs: Add a design document for IOMMU subsystem redesign Teddy Astie
2025-11-20 11:09 ` [RFC PATCH v7 03/14] x86/domain: Defer domain iommu initialization Teddy Astie
2026-08-19 15:08 ` Jan Beulich
2026-08-20 10:10 ` Teddy Astie
2025-11-20 11:09 ` [RFC PATCH v7 04/14] iommu: Move IOMMU domain related structures to (arch_)iommu_context Teddy Astie
2026-08-19 15:15 ` Jan Beulich
2025-11-20 11:09 ` [RFC PATCH v7 05/14] iommu: Simplify quarantine logic Teddy Astie
2026-08-19 15:21 ` Jan Beulich [this message]
2025-11-20 11:09 ` [RFC PATCH v7 06/14] vtd: Remove MAP_ERROR_RECOVERY code path in domain_context_mapping_one Teddy Astie
2026-08-19 15:26 ` Jan Beulich
2025-11-20 11:09 ` [RFC PATCH v7 07/14] iommu: Simplify hardware did management Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 09/14] iommu: Provide 'X' debug key to dump IOMMU context infos Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 08/14] iommu: Introduce redesigned IOMMU subsystem Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 10/14] amd/iommu: Introduce lookup implementation Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 11/14] iommu: Introduce iommu_get_max_iova Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 12/14] x86/iommu: Introduce IOMMU arena Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 13/14] iommu: Introduce PV-IOMMU Teddy Astie
2025-11-20 11:10 ` [RFC PATCH v7 14/14] iommu: Introduce no-dma feature Teddy Astie
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=1e6aa092-778f-4826-8013-aa527a4858eb@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=roger@xenproject.org \
--cc=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.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.