From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH] ArmPlatformPkg/PrePeiCore: seed temporary stack before entering PEI core
Date: Fri, 20 Oct 2017 17:52:20 +0100 [thread overview]
Message-ID: <CAKv+Gu8tFWdot0DaTsmGD-tGhUmuRo64LS0QzF+u6_wVmNZ96g@mail.gmail.com> (raw)
In-Reply-To: <fa2fa397-4c43-66c8-8fdc-46f819edf367@redhat.com>
On 20 October 2017 at 17:51, Laszlo Ersek <lersek@redhat.com> wrote:
> On 10/20/17 18:39, Ard Biesheuvel wrote:
>> On 20 October 2017 at 17:37, Gao, Liming <liming.gao@intel.com> wrote:
>>> Ard:
>>> This case is to share the same value between PeiCore and SecCore. I also think it will be better to define one fixed PCD in MdeModulePkg.dec for this value. Could you submit bugzillar to catch this issue first?
>>>
>>
>> Certainly!
>
> Would it be possible to define the PCD as UINT32, and task 64-bit SEC
> (and PEI_CORE) code to first construct the wider value manually (in a
> register or otherwise)?
>
> Just thinking out loud.
>
Could you think the reasoning behind that out loud as well?
next prev parent reply other threads:[~2017-10-20 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 11:23 [PATCH] ArmPlatformPkg/PrePeiCore: seed temporary stack before entering PEI core Ard Biesheuvel
2017-10-20 13:00 ` Leif Lindholm
2017-10-20 15:43 ` Laszlo Ersek
2017-10-20 16:10 ` Ard Biesheuvel
2017-10-20 16:30 ` Laszlo Ersek
2017-10-20 16:37 ` Gao, Liming
2017-10-20 16:39 ` Ard Biesheuvel
2017-10-20 16:51 ` Laszlo Ersek
2017-10-20 16:52 ` Ard Biesheuvel [this message]
2017-10-20 17:18 ` Laszlo Ersek
2017-10-23 14:18 ` Gao, Liming
2017-10-23 14:39 ` 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=CAKv+Gu8tFWdot0DaTsmGD-tGhUmuRo64LS0QzF+u6_wVmNZ96g@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