From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v2] ArmPlatformPkg/PrePeiCore: seed temporary stack before entering PEI core
Date: Sun, 5 Nov 2017 16:27:12 +0000 [thread overview]
Message-ID: <CAKv+Gu9fmcCCjRumynzcdZgBcMxON_On-WS5Lx3XPsOiH7g-iQ@mail.gmail.com> (raw)
In-Reply-To: <20171105055245.xbicmlagfeu7xt2o@bivouac.eciton.net>
On 5 November 2017 at 05:52, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> On Fri, Nov 03, 2017 at 11:33:52AM +0000, Ard Biesheuvel wrote:
>> DEBUG builds of PEI code will print a diagnostic message regarding
>> the utilization of temporary RAM before switching to permanent RAM.
>> For example,
>>
>> Total temporary memory: 16352 bytes.
>> temporary memory stack ever used: 4820 bytes.
>> temporary memory heap used for HobList: 4720 bytes.
>>
>> Tracking stack utilization like this requires the stack to be seeded
>> with a known magic value, and this needs to occur before entering C
>> code, given that it uses the stack. Currently, only Nt32Pkg appears
>> to implement this feature, but it is useful nonetheless, so let's
>> wire it up for PrePeiCore as well.
>>
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=748
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> OK, this may sound completely unreasonable, but seeing those
> implementations overwrite callee-saved registers without saving them
> makes my brain unhappy. (Yes, I know.)
>
> Could they either:
> - Have a comment prepended establishing the implicit ABI of which
> registers the caller cannot rely on reusing after return.
> Preferably somewhat echoed at the call site.
> - Be rewritten to use only scratch registers?
>
I think it is implied that the startup code does not adhere to the
AAPCS. That code already uses r5 and r6 without stacking them, simply
because we're in the middle of preparing the stack and other execution
context, precisely so the C code we call into can rely on AAPCS
guarantees.
next prev parent reply other threads:[~2017-11-05 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 11:33 [PATCH v2] ArmPlatformPkg/PrePeiCore: seed temporary stack before entering PEI core Ard Biesheuvel
2017-11-05 5:52 ` Leif Lindholm
2017-11-05 16:27 ` Ard Biesheuvel [this message]
2017-11-05 16:29 ` Ard Biesheuvel
2017-11-07 18:09 ` Laszlo Ersek
2017-11-07 18:13 ` Ard Biesheuvel
2017-11-09 21:11 ` Ard Biesheuvel
2017-11-10 9:29 ` Laszlo Ersek
2017-11-10 11:01 ` Ard Biesheuvel
2017-11-08 16:12 ` Leif Lindholm
2017-11-09 21:09 ` Ard Biesheuvel
2017-11-06 4:25 ` Gao, Liming
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=CAKv+Gu9fmcCCjRumynzcdZgBcMxON_On-WS5Lx3XPsOiH7g-iQ@mail.gmail.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