public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: Xiang W <wxjstz@126.com>, <u-boot@lists.denx.de>,
	<anup.patel@wdc.com>, <atish.patra@wdc.com>, <bmeng.cn@gmail.com>,
	<rick@andestech.com>, <lukas.auer@aisec.fraunhofer.de>
Subject: Re: [PATCH v2] riscv: cancel the limitation that NR_CPUS is less than or equal to 32
Date: Fri, 10 Feb 2023 07:25:38 +0000	[thread overview]
Message-ID: <Y+XxcgQenseaXI8W@ubuntu01> (raw)
In-Reply-To: <CAEn-LTr6xzRBak9p7WNjrp_4iMA=jNXnuhQyrzU752smJsdAmQ@mail.gmail.com>

Hi Xiang,

On Fri, Feb 03, 2023 at 03:24:37PM +0100, David Abdurachmanov wrote:
> On Mon, Jan 3, 2022 at 1:13 PM Leo Liang <ycliang@andestech.com> wrote:
> >
> > On Thu, Dec 30, 2021 at 01:55:15AM +0800, Xiang W wrote:
> > > 在 2021-12-29星期三的 17:23 +0800,Leo Liang写道:
> > > > Hi Xiang,
> > > > On Wed, Dec 22, 2021 at 07:32:53AM +0800, Xiang W wrote:
> > > > > Various specifications of riscv allow the number of hart to be
> > > > > greater than 32. The limit of 32 is determined by
> > > > > gd->arch.available_harts. We can eliminate this limitation through
> > > > > bitmaps. Currently, the number of hart is limited to 4095, and 4095
> > > > > is the limit of the RISC-V Advanced Core Local Interruptor
> > > > > Specification.
> > > > >
> > > > > Test on sifive unmatched.
> > > > >
> > > > > Signed-off-by: Xiang W <wxjstz@126.com>
> > > > > ---
> > > > > Changes since v1:
> > > > >
> > > > > * When NR_CPUS is very large, the value of GD_AVAILABLE_HARTS will
> > > > >   overflow the immediate range of ld/lw. This patch fixes this
> > > > >   problem
> > > > >
> > > > >  arch/riscv/Kconfig                   |  4 ++--
> > > > >  arch/riscv/cpu/start.S               | 21 ++++++++++++++++-----
> > > > >  arch/riscv/include/asm/global_data.h |  4 +++-
> > > > >  arch/riscv/lib/smp.c                 |  2 +-
> > > > >  4 files changed, 22 insertions(+), 9 deletions(-)
> > > > >
> 
> I noticed that this has never landed in U-Boot. Was this forgotten or
> dropped for some reason (couldn't find anything)?
> 
> The current limit on the Linux kernel side is 512. The default on
> 64-bit (riscv64) is 64.
> 
> david

The patch seems to cause some CI error (timeout on QEMU).
(https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/15076)
Could you take a look at it if you have time?

Best regards,
Leo

  parent reply	other threads:[~2023-02-10  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 23:32 [PATCH v2] riscv: cancel the limitation that NR_CPUS is less than or equal to 32 Xiang W
2021-12-29  9:23 ` Leo Liang
2021-12-29 17:55   ` Xiang W
2022-01-03 11:11     ` Leo Liang
2023-02-03 14:24       ` David Abdurachmanov
2023-02-06  8:07         ` Leo Liang
2023-02-10  7:25         ` Leo Liang [this message]
2023-02-11 14:11           ` Xiang W
2023-02-13  8:46             ` Leo Liang

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=Y+XxcgQenseaXI8W@ubuntu01 \
    --to=ycliang@andestech.com \
    --cc=anup.patel@wdc.com \
    --cc=atish.patra@wdc.com \
    --cc=bmeng.cn@gmail.com \
    --cc=david.abdurachmanov@gmail.com \
    --cc=lukas.auer@aisec.fraunhofer.de \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=wxjstz@126.com \
    /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