public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Benjamin Doron <benjamin.doron00@gmail.com>,
	Nate DeSimone <nathaniel.l.desimone@intel.com>,
	Isaac Oram <isaac.w.oram@intel.com>
Subject: Re: [edk2-devel] [GSoC 2022] Introducing myself & seeking for project ideas
Date: Tue, 24 May 2022 07:54:30 +0200	[thread overview]
Message-ID: <20220524055430.y4gpdl6iwjcbp75n@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAKbZUD3WBXUnCOrO8X4a8DXJixgcZ9YDTOg8b8w6T9aGBUpXdA@mail.gmail.com>

  Hi,

> > SimicsOpenBoardPkg can partially boot QEMU with a minimum of changes. It
> > makes it into the DXE phase (where we'd eventually get a shell), but fails
> > to initialise SMM, so it can't load the variable driver in there. Many
> > drivers depend on the variable protocol, including critical
> > UEFI-architecture ones, so the DXE core will assert and hang after printing
> > a bunch of "driver GUID discovered but not loaded" messages. To fix this,
> > the SMM access, maybe SMM control drivers would need to be patched; some
> > register definitions differ between chipsets.
> >
> One issue with QEMU is that you currently have 3 machines worth supporting:
> the i440fx (i440fx + PIIX), which is the default, the Q35 (Q35 + ICH9), and
> the microvm (probably not going to be apart of the scope of this project,
> at least for now, even though OVMF supports it).

If you want support for authenticated variables (+ secure boot I guess)
and SMM q35 is pretty much the only option you have.  microvm doesn't
support smm at all, and the i440fx is too old and hasn't enough SMM
memory (no TSEG).

take care,
  Gerd


      parent reply	other threads:[~2022-05-24  5:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 19:35 [GSoC 2022] Introducing myself & seeking for project ideas Théo Jehl
2022-03-31 15:04 ` [edk2-devel] " Pedro Falcato
2022-04-02 12:01   ` Théo Jehl
2022-04-04 21:12     ` Pedro Falcato
2022-04-07 21:36       ` Nate DeSimone
2022-04-08 16:05         ` Théo Jehl
2022-04-13 23:15           ` Nate DeSimone
2022-05-23 16:50             ` Benjamin Doron
2022-05-23 17:33               ` Pedro Falcato
2022-05-23 18:14                 ` Oram, Isaac W
2022-05-24  5:54                 ` Gerd Hoffmann [this message]

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=20220524055430.y4gpdl6iwjcbp75n@sirius.home.kraxel.org \
    --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