From: Marc Zyngier <marc.zyngier@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 0/8] ARMv7: PSCI: add PSCI v1.0 support
Date: Wed, 15 Jun 2016 08:39:50 +0100 [thread overview]
Message-ID: <20160615083950.7f17b9aa@arm.com> (raw)
In-Reply-To: <CAGb2v64pxeNw7G5Wqsmz-HNRkT0wbtp3XO1p-mivo4hsP9wAKA@mail.gmail.com>
On Wed, 15 Jun 2016 15:16:08 +0800
Chen-Yu Tsai <wens@csie.org> wrote:
> Hi,
>
> On Tue, Jun 14, 2016 at 3:01 PM, <macro.wave.z@gmail.com> wrote:
> > From: Hongbo Zhang <hongbo.zhang@nxp.com>
> >
> > v5 changes:
> > - Give up fixing the potential bug of PSCI stack overlap with secure text end
> > when there is more CPUs in system. Because I just want to keep this series as
> > simple as it could be: adding basic PSCI v1.0 support and adding more PSCI
> > v1.0 implements of our platform.
> > While too compplicated patches in assembly language won't call for effective
> > reviews, even I think there is potential bug of PSCI stack, let's fix it in
> > sepetated patch later.
And have silent corruption from the secure side? I hope not.
>
> I've done some patches fixing the stack allocation issue:
>
> https://github.com/wens/u-boot-sunxi/commits/c-psci-part2
>
> These patches are ready, but I want to add a secure data section still.
> The data section will be for variables such as target PC, core/cluster
> power status, context ID, etc.. IMHO this is better than putting stuff
> at the top or bottom of the stack, and can also be referenced directly.
I haven't looked at these patches, but I definitely welcome that kind
of development. Please also consider providing some form of per-cpu
infrastructure (which would in turn solve the issue that Hongbo Zhang
wants to sidestep).
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2016-06-15 7:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:01 [U-Boot] [PATCH v5 0/8] ARMv7: PSCI: add PSCI v1.0 support macro.wave.z at gmail.com
2016-06-14 7:01 ` [U-Boot] [PATCH v5 1/8] ARMv7: PSCI: add PSCI v1.0 functions skeleton macro.wave.z at gmail.com
2016-06-14 7:01 ` [U-Boot] [PATCH v5 2/8] ARMv7: PSCI: factor out reusable psci_cpu_on_common macro.wave.z at gmail.com
2016-06-28 2:49 ` Chen-Yu Tsai
2016-06-28 3:50 ` Hongbo Zhang
2016-06-14 7:01 ` [U-Boot] [PATCH v5 3/8] ARMv7: PSCI: update the place of saving target PC macro.wave.z at gmail.com
2016-06-28 3:24 ` Chen-Yu Tsai
2016-06-28 9:23 ` Hongbo Zhang
2016-06-28 9:48 ` Chen-Yu Tsai
2016-06-14 7:01 ` [U-Boot] [PATCH v5 4/8] ARMv7: PSCI: add codes to save context ID for CPU_ON macro.wave.z at gmail.com
2016-06-28 3:15 ` Chen-Yu Tsai
2016-06-28 10:29 ` Hongbo Zhang
2016-06-14 7:01 ` [U-Boot] [PATCH v5 5/8] ARMv7: PSCI: ls102xa: check target CPU ID before further operations macro.wave.z at gmail.com
2016-06-28 4:10 ` Chen-Yu Tsai
2016-06-28 10:39 ` Hongbo Zhang
2016-06-14 7:01 ` [U-Boot] [PATCH v5 6/8] ARMv7: PSCI: ls102xa: check ALREADY_ON or ON_PENDING for CPU_ON macro.wave.z at gmail.com
2016-06-28 4:30 ` Chen-Yu Tsai
2016-06-30 4:24 ` Hongbo Zhang
2016-06-30 14:47 ` Chen-Yu Tsai
2016-06-14 7:01 ` [U-Boot] [PATCH v5 7/8] ARMv7: PSCI: ls102xa: add more PSCI v1.0 functions implemention macro.wave.z at gmail.com
2016-06-30 14:45 ` Chen-Yu Tsai
2016-06-14 7:01 ` [U-Boot] [PATCH v5 8/8] ARMv7: PSCI: ls102xa: move secure text section into OCRAM macro.wave.z at gmail.com
2016-06-28 4:16 ` Chen-Yu Tsai
2016-06-28 10:45 ` Hongbo Zhang
2016-06-15 7:16 ` [U-Boot] [PATCH v5 0/8] ARMv7: PSCI: add PSCI v1.0 support Chen-Yu Tsai
2016-06-15 7:39 ` Marc Zyngier [this message]
2016-06-15 8:08 ` Hongbo Zhang
2016-06-24 15:26 ` york sun
2016-06-30 5:28 ` Hongbo Zhang
2016-07-04 7:20 ` Hongbo Zhang
2016-07-04 13:11 ` Hans de Goede
2016-07-05 2:26 ` Hongbo Zhang
2016-07-19 20:34 ` york sun
2016-07-21 4:21 ` Hongbo Zhang
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-all 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=20160615083950.7f17b9aa@arm.com \
--to=marc.zyngier@arm.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.