From: "Marvin Häuser" <mhaeuser@posteo.de>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"michael.kubacki@microsoft.com" <michael.kubacki@microsoft.com>
Subject: SecCore evacuation in PeiCore?
Date: Sat, 7 Aug 2021 18:54:50 +0000 [thread overview]
Message-ID: <b8b4e990-5ee6-7152-3806-0f9d30911ce0@posteo.de> (raw)
Good day everyone,
Good day Michael,
The commit that introduced T-RAM evacuation [1] also introduced the
function "MigrateSecModulesInFv()". It also is explicitly mentioned as
part of the control flow in the commit message. As far as I can see,
since then till today this function has never been called anywhere. Was
this some draft function that accidentally made it into the patch, or
did the caller get lost somewhere? The description makes sense to me and
I'm not experienced enough with the PeiCore control flow to tell whether
the PEIM migration somehow covers SecCore implicitly. Also I noticed it
only supports SecCore in a PE/COFF section, not a TE section. Is there a
rationale for that?
Thank you for your time!
Best regards,
Marvin
[1]
https://github.com/tianocore/edk2/commit/9bedaec05b7b8ba9aee248361bb61a85a26726cb
next reply other threads:[~2021-08-07 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 18:54 Marvin Häuser [this message]
2021-08-13 16:51 ` [edk2-devel] SecCore evacuation in PeiCore? Michael Kubacki
2021-08-14 12:29 ` Marvin Häuser
2021-08-16 16:18 ` Michael Kubacki
2021-08-17 6:41 ` Marvin Häuser
2021-08-17 16:16 ` Michael Kubacki
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=b8b4e990-5ee6-7152-3806-0f9d30911ce0@posteo.de \
--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