From: Leo Duran <leo.duran@amd.com>
To: <edk2-devel@ml01.01.org>
Cc: Leo Duran <leo.duran@amd.com>
Subject: [PATCH] MdeModulePkg: Add EFI_GCD_MEMORY_SPACE_NOTIFY_PROTOCOL
Date: Wed, 12 Apr 2017 13:56:39 -0500 [thread overview]
Message-ID: <1492023400-16132-1-git-send-email-leo.duran@amd.com> (raw)
GCD consumes the protocol to issue a Notify() on Add/Remove operations.
The intended use-case is to allow OvmfPkg take actions on behalf of an
SEV-enabled guest.
The new protocol is simply added to the list of optional protocols handled
by DxeMain, and as such leverages the existing DxeProtocolNotify framework.
I will follow this patch with "proof-of-concept" OvmfPkg driver that
installs the protocol to take pertinent actions based on GCD notifications.
Leo Duran (1):
MdeModulePkg: Add EFI_GCD_MEMORY_SPACE_NOTIFY_PROTOCOL
MdeModulePkg/Core/Dxe/DxeMain.h | 10 +++-
MdeModulePkg/Core/Dxe/DxeMain.inf | 4 ++
MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c | 7 +++
MdeModulePkg/Core/Dxe/DxeMain/DxeProtocolNotify.c | 9 ++-
MdeModulePkg/Core/Dxe/Gcd/Gcd.c | 8 +++
.../Include/Protocol/GcdMemorySpaceNotify.h | 65 ++++++++++++++++++++++
MdeModulePkg/MdeModulePkg.dec | 3 +
7 files changed, 100 insertions(+), 6 deletions(-)
create mode 100644 MdeModulePkg/Include/Protocol/GcdMemorySpaceNotify.h
--
2.7.4
next reply other threads:[~2017-04-12 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 18:56 Leo Duran [this message]
2017-04-12 18:56 ` [PATCH] MdeModulePkg: Add EFI_GCD_MEMORY_SPACE_NOTIFY_PROTOCOL Leo Duran
2017-04-12 19:39 ` Kinney, Michael D
2017-04-12 20:32 ` Laszlo Ersek
2017-04-13 0:58 ` Kinney, Michael D
2017-04-13 2:13 ` Zeng, Star
2017-04-13 2:35 ` Duran, Leo
2017-04-13 2:40 ` Yao, Jiewen
2017-04-13 2:44 ` Duran, Leo
2017-04-13 3:05 ` Yao, Jiewen
2017-04-14 14:10 ` Duran, Leo
2017-04-13 2:27 ` Duran, Leo
2017-04-12 20:34 ` 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=1492023400-16132-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