From: Sander Vanheule <sander@svanheule.net>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, linux-mips@vger.kernel.org
Cc: Paul Burton <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org,
INAGAKI Hiroshi <musashino.open@gmail.com>
Subject: Re: [PATCH] MIPS: generic: enable SMP on SMVP systems
Date: Sat, 18 Dec 2021 10:36:35 +0100 [thread overview]
Message-ID: <e570866957f677aab77f2ecb48befc0dcc4481f4.camel@svanheule.net> (raw)
In-Reply-To: <dbff4beb-1982-1568-ab7e-2b12ad956a06@flygoat.com>
Hi Jiaxun,
On Fri, 2021-12-17 at 22:12 +0000, Jiaxun Yang wrote:
>
>
> 在 2021/12/17 18:39, Sander Vanheule 写道:
> > In addition to CPS SMP setups, also try to initialise MT SMP setups with
> > multiple VPEs per CPU core. CMP SMP support is not provided as it is
> > considered deprecated.
> >
> > Additionally, rework the code by dropping the err variable and make it
> > similar to how other platforms perform this initialisation.
> Hi,
>
> Thanks for your patch :-)
>
> However there is a probem that register_vsmp_smp_ops never returns error
> if CONFIG_MIPS_MT_SMP is enabled. But generic kernel is supposed to
> run on systems with & without MT.
>
> So probably you need:
>
> diff --git a/arch/mips/include/asm/smp-ops.h
> b/arch/mips/include/asm/smp-ops.h
> index 65618ff1280c..864aea803984 100644
> --- a/arch/mips/include/asm/smp-ops.h
> +++ b/arch/mips/include/asm/smp-ops.h
> @@ -101,6 +101,9 @@ static inline int register_vsmp_smp_ops(void)
> #ifdef CONFIG_MIPS_MT_SMP
> extern const struct plat_smp_ops vsmp_smp_ops;
>
> + if (!cpu_has_mipsmt)
> + return -ENODEV;
> +
> register_smp_ops(&vsmp_smp_ops);
>
> return 0;
Thanks for the feedback, I was wondering if we had missed something :)
I'll send a v2 (series) including this addition.
Best,
Sander
prev parent reply other threads:[~2021-12-18 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 18:39 Sander Vanheule
2021-12-17 22:12 ` Jiaxun Yang
2021-12-18 9:36 ` Sander Vanheule [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=e570866957f677aab77f2ecb48befc0dcc4481f4.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=musashino.open@gmail.com \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®