From: Sairaj Kodilkar <sarunkod@amd.com>
To: <qemu-devel@nongnu.org>
Cc: <mst@redhat.com>, <vasant.hegde@amd.com>,
<suravee.suthikulpanit@amd.com>,
Sairaj Kodilkar <sarunkod@amd.com>
Subject: [PATCH v2 0/2] Emulated AMD IOMMU cleanup and fixes
Date: Fri, 7 Feb 2025 10:23:52 +0530 [thread overview]
Message-ID: <20250207045354.27329-1-sarunkod@amd.com> (raw)
This series provides few bug fixes for emulated AMD IOMMU. The series is based
on top of qemu upstream master commit d922088eb4ba.
Patch 1: The code was using wrong DTE field to determine interrupt passthrough.
Hence replaced it with correct field according to [1].
Patch 2: Current code sets the PCI capability BAR low and high to the
lower and upper 16 bits of AMDVI_BASE_ADDR respectively, which is
wrong. Instead use 32 bit mask to set the PCI capability BAR low and
high.
The guest IOMMU driver works with current qemu code because it uses
base address from the IVRS table and not the one provided by
PCI capability.
Sairaj Kodilkar (2):
amd_iommu: Use correct DTE field for interrupt passthrough
amd_iommu: Use correct bitmask to set capability BAR
hw/i386/amd_iommu.c | 10 +++++-----
hw/i386/amd_iommu.h | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2025-02-07 4:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 4:53 Sairaj Kodilkar [this message]
2025-02-07 4:53 ` [PATCH 1/2] amd_iommu: Use correct DTE field for interrupt passthrough Sairaj Kodilkar
2025-02-07 4:53 ` [PATCH 2/2] amd_iommu: Use correct bitmask to set capability BAR Sairaj Kodilkar
2025-02-07 4:59 ` [PATCH v2 0/2] Emulated AMD IOMMU cleanup and fixes Arun Kodilkar, Sairaj
2025-02-25 8:47 ` Michael Tokarev
2025-02-26 12:53 ` Vasant Hegde
2025-02-26 15:22 ` Michael Tokarev
2025-02-28 10:04 ` Vasant Hegde
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=20250207045354.27329-1-sarunkod@amd.com \
--to=sarunkod@amd.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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 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.