From: Leo Duran <leo.duran@amd.com>
To: <edk2-devel@lists.01.org>
Cc: <lersek@redhat.com>, <jordan.l.justen@intel.com>,
<feng.tian@intel.com>, <star.zeng@intel.com>,
<maurice.ma@intel.com>, <prince.agyeman@intel.com>,
<ard.biesheuvel@linaro.org>, <brijesh.singh@amd.com>,
Leo Duran <leo.duran@amd.com>
Subject: [RFC v2 0/6] DxeBmDmaLib (BmDmaLib class) library
Date: Fri, 13 Jan 2017 16:14:10 -0600 [thread overview]
Message-ID: <1484345656-3574-1-git-send-email-leo.duran@amd.com> (raw)
This series provides an abstraction layer for Bus-master DMA operations as
currently implemented by the PciHostBridgeDxe driver. The intent is to then
allow override of this library as may be required by specific hardware
implementations, such as AMD's Secure Encrypted Virtualization (SEV).
Please refer to the RFC discussion for SEV here:
http://marc.info/?l=linux-mm&m=147190814023863&w=2
This new (BmDmaLib class) library is cloned from the existing DmaLib with
an additional DmaAbove4GB (BOOLEAN) parameter for the Map and Allocate
interfaces, so that decisions can be made about the need to allocate DMA
buffers below the 4GB boundary.
NOTE: The abstraction layer is intended for Bus-master (DMA capable)
devices, and not restricted to the PCI Root-Bridge use-case. Thus the
rationale for not using EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL_OPERATION types.
Changes since RFC v1:
- Patch 1: Restrict LIBRARY_CLASS to DXE_DRIVER in INF file.
- Patches 2 through 5:
Change Subject: XxxPkg: Resolve BmDmaLib class for PciHostBridgeDxe driver
Add Reviewed-by: Laszlo Ersek <lersek@redhat.com>
- Add clarifications from RFC discussion to this cover letter.
Leo Duran (6):
MdeModulePkg: Add DxeBmDmaLib (BmDmaLib class) library
ArmVirtPkg: Resolve BmDmaLib class for PciHostBridgeDxe driver
CorebootPayloadPkg: Resolve BmDmaLib class for PciHostBridgeDxe driver
MdeModulePkg: Resolve BmDmaLib class for PciHostBridgeDxe driver
OvmfPkg: Resolve BmDmaLib class for PciHostBridgeDxe driver
MdeModulePkg: Modify PciHostBridgeDxe to use new BmDmaLib library
ArmVirtPkg/ArmVirtQemu.dsc | 1 +
ArmVirtPkg/ArmVirtQemuKernel.dsc | 1 +
CorebootPayloadPkg/CorebootPayloadPkgIa32.dsc | 1 +
CorebootPayloadPkg/CorebootPayloadPkgIa32X64.dsc | 1 +
.../Bus/Pci/PciHostBridgeDxe/PciHostBridgeDxe.inf | 1 +
.../Bus/Pci/PciHostBridgeDxe/PciRootBridge.h | 13 +-
.../Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c | 272 +++++----------------
MdeModulePkg/MdeModulePkg.dsc | 3 +
OvmfPkg/OvmfPkgIa32.dsc | 1 +
OvmfPkg/OvmfPkgIa32X64.dsc | 1 +
OvmfPkg/OvmfPkgX64.dsc | 1 +
11 files changed, 76 insertions(+), 220 deletions(-)
--
1.9.1
next reply other threads:[~2017-01-13 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 22:14 Leo Duran [this message]
2017-01-13 22:14 ` [RFC v2 1/6] MdeModulePkg: Add DxeBmDmaLib (BmDmaLib class) library Leo Duran
2017-02-09 1:59 ` Ni, Ruiyu
2017-02-09 15:10 ` Duran, Leo
2017-01-13 22:14 ` [RFC v2 2/6] ArmVirtPkg: Resolve BmDmaLib class for PciHostBridgeDxe driver Leo Duran
2017-01-13 22:14 ` [RFC v2 3/6] CorebootPayloadPkg: " Leo Duran
2017-01-13 22:14 ` [RFC v2 4/6] MdeModulePkg: " Leo Duran
2017-01-13 22:14 ` [RFC v2 5/6] OvmfPkg: " Leo Duran
2017-01-13 22:14 ` [RFC v2 6/6] MdeModulePkg: Modify PciHostBridgeDxe to use new BmDmaLib library Leo Duran
2017-01-17 16:06 ` [RFC v2 0/6] DxeBmDmaLib (BmDmaLib class) library Duran, Leo
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=1484345656-3574-1-git-send-email-leo.duran@amd.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