From: Sairaj Kodilkar <sarunkod@amd.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: <qemu-devel@nongnu.org>, <marcel.apfelbaum@gmail.com>,
<pbonzini@redhat.com>, <richard.henderson@linaro.org>,
<eduardo@habkost.net>, <suravee.suthikulpanit@amd.com>,
<alejandro.j.jimenez@oracle.com>, <joao.m.martins@oracle.com>
Subject: Re: [PATCH v3 0/2] amd_iommu: Fixes
Date: Fri, 16 May 2025 16:15:20 +0530 [thread overview]
Message-ID: <20140492-6040-4010-9b85-da160f06dbca@amd.com> (raw)
In-Reply-To: <20250516063605-mutt-send-email-mst@kernel.org>
On 5/16/2025 4:06 PM, Michael S. Tsirkin wrote:
> On Fri, May 16, 2025 at 03:35:33PM +0530, Sairaj Kodilkar wrote:
>> Fix following two issues in the amd viommu
>> 1. The guest fails to setup the passthrough device when for following setup
>> because amd iommu enables the no DMA memory region even when guest is
>> using DMA remapping mode.
>>
>> -device amd-iommu,intremap=on,xtsup=on,pt=on \
>> -device vfio-pci,host=<DEVID> \
>>
>> and guest forcing DMA remap mode e.g. 'iommu.passthrough=0'
>>
>> which will cause failures from QEMU:
>>
>> qemu-system-x86_64: AHCI: Failed to start DMA engine: bad command list buffer address
>> qemu-system-x86_64: AHCI: Failed to start FIS receive engine: bad FIS receive buffer address
>> qemu-system-x86_64: AHCI: Failed to start DMA engine: bad command list buffer address
>> qemu-system-x86_64: AHCI: Failed to start FIS receive engine: bad FIS receive buffer address
>> qemu-system-x86_64: AHCI: Failed to start DMA engine: bad command list buffer address
>>
>>
>> 2. The guest fails to boot with xtsup=on and <= 255 vCPUs, because amd_iommu
>> does not enable x2apic mode.
>>
>> base commit 56c6e249b6988c1b6edc2dd34ebb0f1e570a1365 (v10.0.0-rc3)
>>
>> Sairaj Kodilkar (1):
>> hw/i386/amd_iommu: Fix device setup failure when PT is on.
>>
>> Vasant Hegde (1):
>> hw/i386/amd_iommu: Fix xtsup when vcpus < 255
>>
>> hw/i386/amd_iommu.c | 20 ++++++++++----------
>> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> changelog?
>
Sorry I forgot to update the cover-letter (Rookie mistake).
Changes Since v2:
Patch 1: Updated commit message [mst]
Patch 2: Updated commit message [mst]
v2:
https://lore.kernel.org/qemu-devel/20250509064526.15500-1-sarunkod@amd.com/
Changes Since v1:
Patch 1: Updated commit message [Alejandro]
Patch 2: None
v1:
https://lore.kernel.org/qemu-devel/20250410064447.29583-1-sarunkod@amd.com/
Regards
Sairaj Kodilkar
>> --
>> 2.34.1
>
next prev parent reply other threads:[~2025-05-16 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 10:05 [PATCH v3 0/2] amd_iommu: Fixes Sairaj Kodilkar
2025-05-16 10:05 ` [PATCH v3 1/2] hw/i386/amd_iommu: Fix device setup failure when PT is on Sairaj Kodilkar
2025-05-16 14:43 ` Philippe Mathieu-Daudé
2025-05-19 3:59 ` Sairaj Kodilkar
2025-05-16 10:05 ` [PATCH v3 2/2] hw/i386/amd_iommu: Fix xtsup when vcpus < 255 Sairaj Kodilkar
2025-05-16 14:38 ` Philippe Mathieu-Daudé
2025-05-19 7:35 ` Vasant Hegde
2025-05-16 10:36 ` [PATCH v3 0/2] amd_iommu: Fixes Michael S. Tsirkin
2025-05-16 10:45 ` Sairaj Kodilkar [this message]
2025-06-02 20:54 ` Michael Tokarev
2025-06-10 8:33 ` Sairaj Kodilkar
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=20140492-6040-4010-9b85-da160f06dbca@amd.com \
--to=sarunkod@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=eduardo@habkost.net \
--cc=joao.m.martins@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=suravee.suthikulpanit@amd.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;
as well as URLs for NNTP newsgroup(s).