From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Demi Marie Obenour" <demiobenour@gmail.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Alyssa Ross" <hi@alyssa.is>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, iommu@lists.linux.dev,
x86@kernel.org, "Spectrum OS Development" <devel@spectrum-os.org>
Subject: Re: Virtio-IOMMU interrupt remapping design
Date: Tue, 17 Jun 2025 20:03:34 -0300 [thread overview]
Message-ID: <20250617230334.GJ1376515@ziepe.ca> (raw)
In-Reply-To: <20250617160103-mutt-send-email-mst@kernel.org>
On Tue, Jun 17, 2025 at 04:01:53PM -0400, Michael S. Tsirkin wrote:
> > On x86 you also need to use remapping to exceed the max CPU count that
> > can be encoded in the MSI, no iommu required to need this.
>
> More of an x86 quirk though, isn't it?
Yes, but so is bundling IOMMU and remapping HW together <shrug>
GIC fully integrates it into the interrupt controller architecture.
Jason
next prev parent reply other threads:[~2025-06-17 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 18:47 Virtio-IOMMU interrupt remapping design Demi Marie Obenour
2025-06-16 13:20 ` Jason Gunthorpe
2025-06-16 16:53 ` Demi Marie Obenour
2025-06-16 17:33 ` Jason Gunthorpe
2025-06-17 19:44 ` Michael S. Tsirkin
2025-06-17 19:57 ` Jason Gunthorpe
2025-06-17 20:01 ` Michael S. Tsirkin
2025-06-17 23:03 ` Jason Gunthorpe [this message]
2025-06-17 19:46 ` Michael S. Tsirkin
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=20250617230334.GJ1376515@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=eperezma@redhat.com \
--cc=hi@alyssa.is \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=jasowang@redhat.com \
--cc=joro@8bytes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox