All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Teddy Astie <teddy.astie@vates.tech>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/5] iommu/vtd: remove non-CX16 logic from interrupt remapping
Date: Mon, 27 Jan 2025 11:04:25 +0100	[thread overview]
Message-ID: <Z5daKcD2hwIfqC8M@macbook.local> (raw)
In-Reply-To: <5395ceb7-60a0-471f-ab23-451ac7937873@suse.com>

On Mon, Jan 27, 2025 at 10:52:47AM +0100, Jan Beulich wrote:
> On 24.01.2025 13:01, Roger Pau Monne wrote:
> > From: Teddy Astie <teddy.astie@vates.tech>
> > 
> > As CX16 support is mandatory for IOMMU usage, the checks for CX16 in the
> > interrupt remapping code are stale.  Remove them together with the
> > associated code introduced in case CX16 was not available.
> 
> Perhaps insert "now" before "mandatory" (then also in patch 3)?

Sure.

Thanks, Roger.


  reply	other threads:[~2025-01-27 10:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 12:01 [PATCH v2 0/5] x86/iommu: make CX16 mandatory for IOMMU Roger Pau Monne
2025-01-24 12:01 ` [PATCH v2 1/5] x86/iommu: check for CMPXCHG16B when enabling IOMMU Roger Pau Monne
2025-01-27  9:51   ` Jan Beulich
2025-01-27 10:03     ` Roger Pau Monné
2025-01-24 12:01 ` [PATCH v2 2/5] iommu/vtd: remove non-CX16 logic from interrupt remapping Roger Pau Monne
2025-01-27  9:52   ` Jan Beulich
2025-01-27 10:04     ` Roger Pau Monné [this message]
2025-01-24 12:01 ` [PATCH v2 3/5] x86/iommu: remove non-CX16 logic from DMA remapping Roger Pau Monne
2025-01-24 12:01 ` [PATCH v2 4/5] iommu/vtd: cleanup MAP_SINGLE_DEVICE and related code Roger Pau Monne
2025-01-24 12:01 ` [PATCH v2 5/5] iommu/amd: atomically update IRTE Roger Pau Monne
2025-01-24 14:24 ` [PATCH for-4.20 v2 0/5] x86/iommu: make CX16 mandatory for IOMMU Andrew Cooper
2025-01-24 14:27   ` Roger Pau Monné
2025-01-27 10:38     ` Oleksii Kurochko

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=Z5daKcD2hwIfqC8M@macbook.local \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --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.