All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH 3/5] vtd: Print originating iommu on faults
Date: Wed, 5 Aug 2026 11:31:49 +0200	[thread overview]
Message-ID: <07e4cde9-cbbe-4ca3-878b-1c72038e4530@suse.com> (raw)
In-Reply-To: <1785319342.8631fc262581453bbf619ec5b2062170.19fad533fa5000e099@vates.tech>

On 29.07.2026 11:59, Teddy Astie wrote:
> When a fault occurs on a IOMMU, print the IOMMU the fault is coming from.
> 
> Signed-off-by: Teddy Astie <teddy.astie@vates.tech>

Acked-by: Jan Beulich <jbeulich@suse.com>

Nevertheless I think this doesn't go quite far enough - this internal index,
to be helpful, would need associating back to the respective firmware data.
What iommu_alloc() logs is not only limited to verbose mode, but also doesn't
include the index. I think something need doing there, and then we need to be
more consistent throughout to include the IOMMU index in log messages
pertaining to a particular IOMMU.

Jan


  reply	other threads:[~2026-08-05  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  9:59 [PATCH 0/5] Misc VT-d changes Teddy Astie
2026-07-29  9:59 ` [PATCH 2/5] vtd: Ensure context entry is cleared properly Teddy Astie
2026-08-04 16:04   ` Jan Beulich
2026-07-29  9:59 ` [PATCH 3/5] vtd: Print originating iommu on faults Teddy Astie
2026-08-05  9:31   ` Jan Beulich [this message]
2026-07-29  9:59 ` [PATCH 4/5] vtd: Don't disable hwdom passthrough on unhandled SAGAW bits Teddy Astie
2026-08-05  9:41   ` Jan Beulich
2026-07-29  9:59 ` [PATCH 5/5] vtd: Move intremap table to xenheap Teddy Astie
2026-08-05  9:44   ` Jan Beulich
2026-08-05 10:06     ` Andrew Cooper
2026-08-05 12:42       ` Teddy Astie
2026-07-29 10:05 ` [RESEND PATCH 1/5] vtd: Ensure root entry is updated consistently Teddy Astie
2026-08-04 15:58   ` Jan Beulich
2026-08-05 13:03     ` 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=07e4cde9-cbbe-4ca3-878b-1c72038e4530@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.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.