From: "Corvin Köhne" <c.koehne@beckhoff.com>
To: <qemu-devel@nongnu.org>
Cc: "Cédric Le Goater" <clg@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>
Subject: [PATCH 0/7] vfio/igd: add passthrough support for IGDs of gen 11 and later
Date: Thu, 22 Aug 2024 13:08:25 +0200 [thread overview]
Message-ID: <20240822111819.34306-1-c.koehne@beckhoff.com> (raw)
Hi,
Qemu has experimental support for GPU passthrough of Intels integrated graphic
devices. Unfortunately, Intel has changed some bits for their gen 11 devices
and later. To support these devices, we have to account for those changes. This
patch series adds the missing bits on the Qemu side.
I've tested the patch series on an ElkhartLake and TigerLake device. On the
guest side, I've tested an EFI environment (GOP driver), a Linux guest and a
Windows VM. The driver of all guests are able to use the GPU and produce an
output on the connected display.
Corvin Köhne (7):
vfio/igd: return an invalid generation for unknown devices
vfio/igd: support legacy mode for all known generations
vfio/igd: use new BDSM register location and size for gen 11 and later
vfio/igd: add new bar0 quirk to emulate BDSM mirror
vfio/igd: add ID's for ElkhartLake and TigerLake
vfio/igd: don't set stolen memory size to zero
vfio/igd: correctly calculate stolen memory size for gen 9 and later
hw/vfio/igd.c | 184 +++++++++++++++++++++++++++++++++++++------
hw/vfio/pci-quirks.c | 1 +
hw/vfio/pci.h | 1 +
3 files changed, 160 insertions(+), 26 deletions(-)
--
2.46.0
This email contains confidential information. If you have received it in error, you must not read, use, copy or pass on this e-mail or its attachments. If you have received the e-mail in error, please inform me immediately by reply e-mail and then delete this e-mail from your system. Thank you
Diese E-Mail enthält vertrauliche Informationen. Sollten Sie sie irrtümlich erhalten haben, dürfen Sie diese E-Mail oder ihre Anhänge nicht lesen, verwenden, kopieren oder weitergeben. Sollten Sie die Mail versehentlich erhalten haben, teilen Sie mir dies bitte umgehend per Antwort-E-Mail mit und löschen Sie diese E-Mail dann aus Ihrem System. Vielen Dank
Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans Beckhoff
Registered office: Verl, Germany | Register court: Guetersloh HRA 7075
next reply other threads:[~2024-08-22 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 11:08 Corvin Köhne [this message]
2024-08-22 11:08 ` [PATCH 1/7] vfio/igd: return an invalid generation for unknown devices Corvin Köhne
2024-08-22 11:08 ` [PATCH 2/7] vfio/igd: support legacy mode for all known generations Corvin Köhne
2024-08-22 11:08 ` [PATCH 3/7] vfio/igd: use new BDSM register location and size for gen 11 and later Corvin Köhne
2024-08-22 11:08 ` [PATCH 4/7] vfio/igd: add new bar0 quirk to emulate BDSM mirror Corvin Köhne
2024-08-26 16:35 ` Alex Williamson
2024-08-28 10:40 ` Corvin Köhne
2024-08-28 12:50 ` Corvin Köhne
2024-08-28 13:08 ` Cédric Le Goater
2024-08-22 13:54 ` [PATCH 5/7] vfio/igd: add ID's for ElkhartLake and TigerLake Corvin Köhne
2024-08-22 13:54 ` [PATCH 6/7] vfio/igd: don't set stolen memory size to zero Corvin Köhne
2024-08-22 13:54 ` [PATCH 7/7] vfio/igd: correctly calculate stolen memory size for gen 9 and later Corvin Köhne
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=20240822111819.34306-1-c.koehne@beckhoff.com \
--to=c.koehne@beckhoff.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).