From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Brijesh Singh <brijesh.singh@amd.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: [PATCH 0/6] OvmfPkg/VirtioGpuDxe: map system memory addresses to device addresses
Date: Mon, 28 Aug 2017 15:24:30 +0200 [thread overview]
Message-ID: <20170828132436.15933-1-lersek@redhat.com> (raw)
Repo: https://github.com/lersek/edk2.git
Branch: virtio_gpu_map
This series brings IOMMU support to VirtioGpuDxe. The interesting part
is patch#5.
I formatted the patches with function context, for easier review.
I regression-tested this series in various environments; IA32, X64,
AARCH64. My access to a SEV machine is still in the making, so I
couldn't test the patches on SEV.
Brijesh, if you could test the series for me on SEV, that would be
great. I also plan to test it on SEV, once my access is established.
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Brijesh Singh <brijesh.singh@amd.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Thanks,
Laszlo
Laszlo Ersek (6):
OvmfPkg/VirtioGpuDxe: map VRING for bus master common buffer operation
OvmfPkg/VirtioGpuDxe: map virtio GPU command objects to device
addresses
OvmfPkg/VirtioGpuDxe: take EFI_PHYSICAL_ADDRESS in
ResourceAttachBacking()
OvmfPkg/VirtioGpuDxe: helpers for backing store
(de)allocation+(un)mapping
OvmfPkg/VirtioGpuDxe: map backing store to bus master device address
OvmfPkg/VirtioGpuDxe: negotiate VIRTIO_F_IOMMU_PLATFORM
OvmfPkg/VirtioGpuDxe/VirtioGpu.h | 89 ++++++-
OvmfPkg/VirtioGpuDxe/Commands.c | 263 ++++++++++++++++++--
OvmfPkg/VirtioGpuDxe/DriverBinding.c | 1 -
OvmfPkg/VirtioGpuDxe/Gop.c | 62 +++--
4 files changed, 370 insertions(+), 45 deletions(-)
--
2.14.1.3.gb7cf6e02401b
next reply other threads:[~2017-08-28 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 13:24 Laszlo Ersek [this message]
2017-08-28 13:24 ` [PATCH 1/6] OvmfPkg/VirtioGpuDxe: map VRING for bus master common buffer operation Laszlo Ersek
2017-08-28 13:24 ` [PATCH 2/6] OvmfPkg/VirtioGpuDxe: map virtio GPU command objects to device addresses Laszlo Ersek
2017-08-28 13:24 ` [PATCH 3/6] OvmfPkg/VirtioGpuDxe: take EFI_PHYSICAL_ADDRESS in ResourceAttachBacking() Laszlo Ersek
2017-08-28 13:24 ` [PATCH 4/6] OvmfPkg/VirtioGpuDxe: helpers for backing store (de)allocation+(un)mapping Laszlo Ersek
2017-08-28 13:24 ` [PATCH 5/6] OvmfPkg/VirtioGpuDxe: map backing store to bus master device address Laszlo Ersek
2017-08-28 13:24 ` [PATCH 6/6] OvmfPkg/VirtioGpuDxe: negotiate VIRTIO_F_IOMMU_PLATFORM Laszlo Ersek
2017-08-29 23:02 ` [PATCH 0/6] OvmfPkg/VirtioGpuDxe: map system memory addresses to device addresses Laszlo Ersek
2017-08-30 15:47 ` Brijesh Singh
2017-08-30 16:15 ` Laszlo Ersek
2017-09-01 12:31 ` Laszlo Ersek
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=20170828132436.15933-1-lersek@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