public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Andes <uboot@andestech.com>
Cc: <u-boot@lists.denx.de>, <bmeng.cn@gmail.com>,
	<lukas.auer@aisec.fraunhofer.de>, <anup@brainfault.org>,
	<atishp@atishpatra.org>, <xypron.glpk@gmx.de>,
	<nikita.shubin@maquefel.me>, <seanga2@gmail.com>,
	<rick@andestech.com>, <rickchen36@gmail.com>
Subject: Re: [PATCH 1/2] riscv: Introduce AVAILABLE_HARTS
Date: Thu, 22 Sep 2022 03:32:19 +0000	[thread overview]
Message-ID: <YyvXQ/2DVeh8ZyxC@ubuntu01> (raw)
In-Reply-To: <20220921063455.7814-1-uboot@andestech.com>

On Wed, Sep 21, 2022 at 02:34:54PM +0800, Andes wrote:
> From: Rick Chen <rick@andestech.com>
> 
> In SMP all harts will register themself in available_hart
> during start up. Then main hart will send IPI to other harts
> according to this variables. But this mechanism may not
> guarantee that all other harts can jump to next stage.
> 
> When main hart is sending IPI to other hart according to
> available_harts, but other harts maybe still not finish the
> registration. Then the SMP booting will miss some harts finally.
> So let it become an option and it will be enabled by default.
> 
> Please refer to the discussion:
> https://www.mail-archive.com/u-boot@lists.denx.de/msg449997.html
> 
> Signed-off-by: Rick Chen <rick@andestech.com>
> ---
>  arch/riscv/Kconfig                   |  7 +++++++
>  arch/riscv/cpu/cpu.c                 |  2 ++
>  arch/riscv/cpu/start.S               | 13 ++++++++-----
>  arch/riscv/include/asm/global_data.h |  2 ++
>  arch/riscv/lib/asm-offsets.c         |  2 ++
>  arch/riscv/lib/smp.c                 |  2 ++
>  6 files changed, 23 insertions(+), 5 deletions(-)

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

      parent reply	other threads:[~2022-09-22  3:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  6:34 [PATCH 1/2] riscv: Introduce AVAILABLE_HARTS Andes
2022-09-21  6:34 ` [PATCH 2/2] riscv: ae350: Disable AVAILABLE_HARTS Andes
2022-09-22  3:33   ` Leo Liang
2022-09-22  3:32 ` Leo Liang [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-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=YyvXQ/2DVeh8ZyxC@ubuntu01 \
    --to=ycliang@andestech.com \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=bmeng.cn@gmail.com \
    --cc=lukas.auer@aisec.fraunhofer.de \
    --cc=nikita.shubin@maquefel.me \
    --cc=rick@andestech.com \
    --cc=rickchen36@gmail.com \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot@andestech.com \
    --cc=xypron.glpk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox