From: Sander Vanheule <sander@svanheule.net>
To: linux-mips@vger.kernel.org
Cc: INAGAKI Hiroshi <musashino.open@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paul Burton <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>
Subject: [PATCH v2 1/2] MIPS: only register MT SMP ops if MT is supported
Date: Sat, 18 Dec 2021 11:05:10 +0100 [thread overview]
Message-ID: <20211218100511.42508-2-sander@svanheule.net> (raw)
In-Reply-To: <20211218100511.42508-1-sander@svanheule.net>
Verify that the current CPU actually supports multi-threading before
registering MT SMP ops, instead of unconditionally registering them if
the kernel is compiled with CONFIG_MIPS_MT_SMP.
Suggested-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
arch/mips/include/asm/smp-ops.h | 3 +++
1 file changed, 3 insertions(+)
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;
--
2.33.1
next prev parent reply other threads:[~2021-12-18 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 10:05 [PATCH v2 0/2] Support MT SMP on generic MIPS kernel Sander Vanheule
2021-12-18 10:05 ` Sander Vanheule [this message]
2021-12-18 10:05 ` [PATCH v2 2/2] MIPS: generic: enable SMP on SMVP systems Sander Vanheule
2021-12-21 13:56 ` [PATCH v2 0/2] Support MT SMP on generic MIPS kernel 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=20211218100511.42508-2-sander@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;
as well as URLs for NNTP newsgroup(s).