From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH] Add QemuIGDHelperDxe
Date: Wed, 25 Apr 2018 15:59:02 +0200 [thread overview]
Message-ID: <4c9cf49a-4f24-c443-1bba-cdabc204aea6@redhat.com> (raw)
In-Reply-To: <20180425121312.26424-1-kraxel@redhat.com>
Hi Gerd,
On 04/25/18 14:13, Gerd Hoffmann wrote:
> Little driver to setup the OpRegion for Intel vgpu devices.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> OvmfPkg/QemuIGDHelperDxe/QemuIGDHelper.c | 262 ++++++++++++++++++++++++++
> OvmfPkg/OvmfPkgIa32.dsc | 1 +
> OvmfPkg/OvmfPkgIa32.fdf | 1 +
> OvmfPkg/OvmfPkgIa32X64.dsc | 1 +
> OvmfPkg/OvmfPkgIa32X64.fdf | 1 +
> OvmfPkg/OvmfPkgX64.dsc | 1 +
> OvmfPkg/OvmfPkgX64.fdf | 1 +
> OvmfPkg/QemuIGDHelperDxe/QemuIGDHelperDxe.inf | 32 ++++
> 8 files changed, 300 insertions(+)
> create mode 100644 OvmfPkg/QemuIGDHelperDxe/QemuIGDHelper.c
> create mode 100644 OvmfPkg/QemuIGDHelperDxe/QemuIGDHelperDxe.inf
I wrote the exact same driver last week, functionally speaking, and
indeed it "works" (reportedly).
But, it's not the right thing to do. Please see:
https://bugzilla.tianocore.org/show_bug.cgi?id=935
As I wrote there, the right thing to do is one of the following two options:
(a) OS-level drivers for the GVT-g VGPU should be liberated of ACPI and
other firmware-level dependencies, and become pure PCI(e) drivers.
(b) alternatively, Intel should provide a standalone, complete UEFI
driver for the GVT-g VGPU, that sets up all the artifacts for the
OS-level driver as well, without relying on fw_cfg or other platform
hacks. This driver should exist as a file on the EFI system partition,
or (better) in the ROM BAR of the assigned device.
Changbin Du's comment at
<https://bugzilla.tianocore.org/show_bug.cgi?id=935#c8> seems to imply
that (b) could happen in practice.
Thanks!
Laszlo
prev parent reply other threads:[~2018-04-25 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 12:13 [PATCH] Add QemuIGDHelperDxe Gerd Hoffmann
2018-04-25 13:59 ` Laszlo Ersek [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-list 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=4c9cf49a-4f24-c443-1bba-cdabc204aea6@redhat.com \
--to=devel@edk2.groups.io \
/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