public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io
Cc: "Oliver Steffen" <osteffen@redhat.com>,
	"László Érsek" <lersek@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [edk2-devel] [PATCH 0/7] Add VirtMmCommunication driver, enable for OVMF and ArmVirt.
Date: Thu, 23 Nov 2023 16:02:27 +0100	[thread overview]
Message-ID: <20231123150234.117835-1-kraxel@redhat.com> (raw)

This is the edk2 side of the qemu patch series posted last week to
qemu-devel:
  https://lists.gnu.org/archive/html/qemu-devel/2023-11/msg03714.html

The driver forwards MM calls to the virtualization host instead of the
MM code running in SMM (x64) or el3 (arm) mode.  The functionality
traditionally implemented by the SMM code is provided by qemu instead.

This allows to provide persistent variable support without an
(virtual) flash device and it also allows to support secure
boot without depending on SMM or el3 emulation support in the
hypervisor.

take care,
  Gerd

Gerd Hoffmann (7):
  OvmfPkg: add IndustryStandard/QemuUefiVars.h
  OvmfPkg: add new VirtMmCommunicationDxe driver
  OvmfPkg/OvmfPkgX64: add QEMU_VARS option
  OvmfPkg: add PcdQemuVarsRequire
  OvmfPkg/VirtMmCommunicationDxe: stop on init failure
  OvmfPkg/VirtMmCommunicationDxe: add arm support
  ArmVirtPkg/ArmVirtQemu: add QEMU_VARS option

 OvmfPkg/OvmfPkg.dec                           |   3 +
 ArmVirtPkg/ArmVirt.dsc.inc                    |   3 +
 ArmVirtPkg/ArmVirtQemu.dsc                    |  11 +
 ArmVirtPkg/ArmVirtQemuKernel.dsc              |  11 +
 OvmfPkg/OvmfPkgX64.dsc                        |  17 +-
 OvmfPkg/OvmfPkgX64.fdf                        |  12 +-
 OvmfPkg/PlatformPei/PlatformPei.inf           |   1 +
 .../VirtMmCommunication.inf                   |  67 +++
 .../Include/IndustryStandard/QemuUefiVars.h   |  41 ++
 .../VirtMmCommunication.h                     |  37 ++
 OvmfPkg/PlatformPei/Platform.c                |   4 +
 OvmfPkg/VirtMmCommunicationDxe/QemuFdt.c      | 208 ++++++++++
 OvmfPkg/VirtMmCommunicationDxe/QemuX64.c      | 106 +++++
 .../VirtMmCommunication.c                     | 390 ++++++++++++++++++
 ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc          |   5 +
 15 files changed, 914 insertions(+), 2 deletions(-)
 create mode 100644 OvmfPkg/VirtMmCommunicationDxe/VirtMmCommunication.inf
 create mode 100644 OvmfPkg/Include/IndustryStandard/QemuUefiVars.h
 create mode 100644 OvmfPkg/VirtMmCommunicationDxe/VirtMmCommunication.h
 create mode 100644 OvmfPkg/VirtMmCommunicationDxe/QemuFdt.c
 create mode 100644 OvmfPkg/VirtMmCommunicationDxe/QemuX64.c
 create mode 100644 OvmfPkg/VirtMmCommunicationDxe/VirtMmCommunication.c

-- 
2.42.0



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111684): https://edk2.groups.io/g/devel/message/111684
Mute This Topic: https://groups.io/mt/102767943/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



             reply	other threads:[~2023-11-23 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 15:02 Gerd Hoffmann [this message]
2023-11-23 15:02 ` [edk2-devel] [PATCH 1/7] OvmfPkg: add IndustryStandard/QemuUefiVars.h Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 2/7] OvmfPkg: add new VirtMmCommunicationDxe driver Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 3/7] OvmfPkg/OvmfPkgX64: add QEMU_VARS option Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 4/7] OvmfPkg: add PcdQemuVarsRequire Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 5/7] OvmfPkg/VirtMmCommunicationDxe: stop on init failure Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 6/7] OvmfPkg/VirtMmCommunicationDxe: add arm support Gerd Hoffmann
2023-11-23 15:02 ` [edk2-devel] [PATCH 7/7] ArmVirtPkg/ArmVirtQemu: add QEMU_VARS option Gerd Hoffmann
2023-11-28  8:33 ` [edk2-devel] [PATCH 0/7] Add VirtMmCommunication driver, enable for OVMF and ArmVirt Ard Biesheuvel

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=20231123150234.117835-1-kraxel@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