From: Daniil Egranov <daniil.egranov@arm.com>
To: edk2-devel@lists.01.org
Cc: leif.lindholm@linaro.org, ard.biesheuvel@linaro.org,
Daniil Egranov <daniil.egranov@arm.com>
Subject: [PATCH 0/4] Virtio non-discoverable devices
Date: Tue, 6 Mar 2018 19:36:33 -0600 [thread overview]
Message-ID: <20180307013637.16462-1-daniil.egranov@arm.com> (raw)
This is an attempt to add MMIO Virtio devices into the
non-discoverable device registration procedure and allow
Virtio PCI drivers to recognize and program such devices
correctly.
The main issue is that the set of MMIO registers is different
from PCI, plus the width of similar registers are not
always the same. The code implements the translation of
the PCI IO registers to MMIO registers.
Another difference between PCI and MMIO Virtio devices found
during the testing is that MMIO devices may require more
registers to be programmed compared to PCI. The VirtioPciDeviceDxe
was patched to detect non-discoverable MMIO devices and allow
calling a PCI MemIo protocol function.
This set of patches was tested with MMIO Virtio Block and
Virtio Net devices.
Daniil Egranov (4):
MdeModulePkg: Added new Virtio non-discoverable type and GUID
NonDiscoverableDeviceRegistrationLib: Added Virtio support
NonDiscoverablePciDeviceDxe: Added MMIO Virtio support
VirtioPciDeviceDxe: Added non-discoverable Virtio support
.../NonDiscoverablePciDeviceDxe.c | 3 +-
.../NonDiscoverablePciDeviceDxe.inf | 5 +-
.../NonDiscoverablePciDeviceIo.c | 240 ++++++++++++++++++++-
MdeModulePkg/Include/Guid/NonDiscoverableDevice.h | 3 +
.../Library/NonDiscoverableDeviceRegistrationLib.h | 1 +
.../NonDiscoverableDeviceRegistrationLib.c | 3 +
.../NonDiscoverableDeviceRegistrationLib.inf | 1 +
MdeModulePkg/MdeModulePkg.dec | 1 +
OvmfPkg/VirtioPciDeviceDxe/VirtioPciDevice.c | 143 +++++++++++-
OvmfPkg/VirtioPciDeviceDxe/VirtioPciDevice.h | 21 +-
OvmfPkg/VirtioPciDeviceDxe/VirtioPciDeviceDxe.inf | 4 +-
OvmfPkg/VirtioPciDeviceDxe/VirtioPciFunctions.c | 117 +++++++++-
12 files changed, 528 insertions(+), 14 deletions(-)
--
2.11.0
next reply other threads:[~2018-03-07 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 1:36 Daniil Egranov [this message]
2018-03-07 1:36 ` [PATCH 1/4] MdeModulePkg: Added new Virtio non-discoverable type and GUID Daniil Egranov
2018-03-07 1:36 ` [PATCH 2/4] NonDiscoverableDeviceRegistrationLib: Added Virtio support Daniil Egranov
2018-03-07 1:36 ` [PATCH 3/4] NonDiscoverablePciDeviceDxe: Added MMIO " Daniil Egranov
2018-03-07 1:36 ` [PATCH 4/4] VirtioPciDeviceDxe: Added non-discoverable " Daniil Egranov
2018-03-07 8:03 ` [PATCH 0/4] Virtio non-discoverable devices Ard Biesheuvel
2018-03-07 20:18 ` Laszlo Ersek
2018-03-08 8:21 ` Daniil Egranov
2018-03-08 8:29 ` Ard Biesheuvel
2018-03-12 6:19 ` Daniil Egranov
2018-03-12 7:31 ` Ard Biesheuvel
2018-03-07 10:56 ` Laszlo Ersek
2018-03-13 2:55 ` Daniil Egranov
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=20180307013637.16462-1-daniil.egranov@arm.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