From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH 1/3] MIPS: Rework smt cmdline parameters
Date: Fri, 9 Jun 2023 10:36:29 +0200 [thread overview]
Message-ID: <20230609083629.GA9563@alpha.franken.de> (raw)
In-Reply-To: <20230521223124.21911-2-jiaxun.yang@flygoat.com>
On Sun, May 21, 2023 at 11:31:22PM +0100, Jiaxun Yang wrote:
> Provide a generic smt parameters interface aligned with s390
> to allow users to limit smt usage and threads per core.
>
> It replaced previous undocumented "nothreads" parameter for
> smp-cps which is ambiguous and does not cover smp-mt.
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> .../admin-guide/kernel-parameters.txt | 4 ++--
> arch/mips/include/asm/smp.h | 2 ++
> arch/mips/kernel/smp-cps.c | 13 +------------
> arch/mips/kernel/smp-mt.c | 3 ++-
> arch/mips/kernel/smp.c | 18 ++++++++++++++++++
> 5 files changed, 25 insertions(+), 15 deletions(-)
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:[~2023-06-09 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 22:31 [PATCH 0/3] MIPS: Enhancements on usage and documentation of parameters Jiaxun Yang
2023-05-21 22:31 ` [PATCH 1/3] MIPS: Rework smt cmdline parameters Jiaxun Yang
2023-06-09 8:36 ` Thomas Bogendoerfer [this message]
2023-05-21 22:31 ` [PATCH 2/3] MIPS: Select CONFIG_GENERIC_IDLE_POLL_SETUP Jiaxun Yang
2023-06-09 8:36 ` Thomas Bogendoerfer
2023-05-21 22:31 ` [PATCH 3/3] Documentation: kernel-parameters: Add some MIPS parameters Jiaxun Yang
2023-05-21 23:10 ` Randy Dunlap
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=20230609083629.GA9563@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=corbet@lwn.net \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
/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).