From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: "Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: SMP: Implement parallel CPU bring up for EyeQ
Date: Sun, 27 Apr 2025 09:53:47 +0200 [thread overview]
Message-ID: <aA3ii5ilAEc-z-ID@alpha.franken.de> (raw)
In-Reply-To: <20250413-parallel-cpu-bringup-v1-1-a19d36ec229b@bootlin.com>
On Sun, Apr 13, 2025 at 09:12:32PM +0200, Gregory CLEMENT wrote:
> Added support for starting CPUs in parallel on EyeQ to speed up boot time.
>
> On EyeQ5, booting 8 CPUs is now ~90ms faster.
> On EyeQ6, booting 32 CPUs is now ~650ms faster.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> Hello,
>
> This patch allows CPUs to start in parallel. It has been tested on
> EyeQ5 and EyeQ6, which are both MIPS64 and use the I6500 design. These
> systems use CPS to support SMP.
>
> As noted in the commit log, on EyeQ6, booting 32 CPUs is now ~650ms
> faster.
>
> Currently, this support is only for EyeQ SoC. However, it should also
> work for other CPUs using CPS. I am less sure about MT ASE support,
> but this patch can be a good starting point. If anyone wants to add
> support for other systems, I can share some ideas, especially for the
> MIPS_GENERIC setup that needs to handle both types of SMP setups.
>
> Gregory
> ---
> arch/mips/Kconfig | 2 ++
> arch/mips/include/asm/topology.h | 3 +++
> arch/mips/kernel/smp-cps.c | 2 ++
> arch/mips/kernel/smp.c | 18 ++++++++++++++++++
> 4 files changed, 25 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2025-04-27 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 19:12 Gregory CLEMENT
2025-04-27 7:53 ` Thomas Bogendoerfer [this message]
2025-04-27 10:13 ` Huacai Chen
2025-04-30 3:20 ` Huacai Chen
2025-04-30 7:09 ` Gregory CLEMENT
2025-04-30 7:21 ` Huacai Chen
2025-04-30 7:31 ` Gregory CLEMENT
2025-05-02 15:32 ` Gregory CLEMENT
2025-05-02 22:03 ` Thomas Bogendoerfer
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=aA3ii5ilAEc-z-ID@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=gregory.clement@bootlin.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.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
all inboxes | Powered by JetHome®