From: Brijesh Singh <brijesh.singh@amd.com>
To: edk2-devel@lists.01.org
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Brijesh Singh <brijesh.singh@amd.com>
Subject: [PATCH v3 0/1] Use BusMasterCommonBuffer to map FW_CFG_DMA_ACCESS
Date: Thu, 3 Aug 2017 19:11:11 -0400 [thread overview]
Message-ID: <1501801872-22626-1-git-send-email-brijesh.singh@amd.com> (raw)
The patch applies on top of Laszlo's IoMmuDxe cleanup series [1].
Commit is also available at https://github.com/codomania/edk2/tree/qemufwcfg-sev
[1] https://lists.01.org/pipermail/edk2-devel/2017-August/012808.html
Changes since v2:
* Changes to address v2 feedbacks.
Changes since v1:
* Drop Patch 1 through 3, they are covered by Laszlo's cleanup series
* Rebase to the latest
Brijesh Singh (1):
OvmfPkg/QemuFwCfgLib: Use BusMasterCommonBuffer to map
FW_CFG_DMA_ACCESS
OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgLibInternal.h | 42 +--
OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgDxe.c | 330 ++++++++++++++++----
OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgLib.c | 130 --------
OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgPei.c | 99 +++---
OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgSec.c | 58 +---
5 files changed, 367 insertions(+), 292 deletions(-)
--
2.7.4
next reply other threads:[~2017-08-03 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 23:11 Brijesh Singh [this message]
2017-08-03 23:11 ` [PATCH v3 1/1] OvmfPkg/QemuFwCfgLib: Use BusMasterCommonBuffer to map FW_CFG_DMA_ACCESS Brijesh Singh
2017-08-04 2:47 ` Issue of step by step debugging of OVMF SEC code in QEMU wang xiaofeng
[not found] ` <14E6BF08-E850-4DBD-BA6E-EE1ED90B97AA@apple.com>
2017-08-04 3:26 ` wang xiaofeng
2017-08-04 3:41 ` wang xiaofeng
2017-08-04 4:35 ` Andrew Fish
2017-08-05 1:32 ` [PATCH v3 1/1] OvmfPkg/QemuFwCfgLib: Use BusMasterCommonBuffer to map FW_CFG_DMA_ACCESS Laszlo Ersek
2017-08-04 23:07 ` [PATCH v3 0/1] " 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=1501801872-22626-1-git-send-email-brijesh.singh@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