From: Vasant Hegde <vasant.hegde@amd.com>
To: "César Zapata" <el_caesar@outlook.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"Suravee Suthikulpanit" <suravee.suthikulpanit@amd.com>
Cc: "suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG][AMD IOMMU][VFIO] IVMD exclusion ranges block GPU passthrough on ASUS GA403UI, reproduced on 7.4-rc0
Date: Fri, 23 Oct 2026 11:51:46 +0530 [thread overview]
Message-ID: <b7d3a4f4-0ab2-45e9-b9b0-8ea9dc0b2b3e@amd.com> (raw)
In-Reply-To: <RO2P152MB51059B868259A82B182943F48D652@RO2P152MB5105.LAMP152.PROD.OUTLOOK.COM>
Hi Cesar,
On 10/22/2026 11:22 PM, César Zapata wrote:
> Algunos contactos que recibieron este mensaje no suelen recibir correos electrónicos de el_caesar@outlook.com. Por qué es esto importante<https://aka.ms/LearnAboutSenderIdentification>
> Hello,
> I would like to report a reproducible AMD IOMMU/VFIO issue on an ASUS ROG Zephyrus G14 GA403UI, now confirmed using an upstream Linux Mainline Vanilla 7.4.0-rc0 kernel without the proprietary NVIDIA driver.
> The firmware publishes broad IVMD exclusion ranges that Linux exposes as IOMMU_RESV_DIRECT. Consequently, VFIO refuses to establish an IOMMU domain for an otherwise isolated NVIDIA GPU.
> System information
Thanks for the report. I believe below mention series should fix this issue.
@Suravee, Can you respin the series?
-Vasant
prev parent reply other threads:[~2026-10-23 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RO2P152MB51059B868259A82B182943F48D652@RO2P152MB5105.LAMP152.PROD.OUTLOOK.COM>
2026-10-22 17:57 ` César Zapata
2026-10-23 6:21 ` Vasant Hegde [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=b7d3a4f4-0ab2-45e9-b9b0-8ea9dc0b2b3e@amd.com \
--to=vasant.hegde@amd.com \
--cc=el_caesar@outlook.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®