From: Serge Semin <fancer.lancer@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Matthew Wilcox <willy@infradead.org>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Arnd Bergmann <arnd@arndb.de>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Aleksandar Rikalo <arikalo@gmail.com>,
Dragan Mladjenovic <dragan.mladjenovic@syrmia.com>,
Chao-ying Fu <cfu@wavecomp.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Yinglu Yang <yangyinglu@loongson.cn>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Marc Zyngier <maz@kernel.org>,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 7/7] mips: Set dump-stack arch description
Date: Wed, 22 Nov 2023 21:24:05 +0300 [thread overview]
Message-ID: <20231122182419.30633-8-fancer.lancer@gmail.com> (raw)
In-Reply-To: <20231122182419.30633-1-fancer.lancer@gmail.com>
In the framework of the MIPS architecture the mips_set_machine_name()
method is defined to set the machine name. The name currently is only used
in the /proc/cpuinfo file content generation. Let's have it utilized to
mach-personalize the dump-stack data too in a way it's done on ARM, ARM64,
RISC-V, etc.
Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
---
arch/mips/kernel/prom.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/mips/kernel/prom.c b/arch/mips/kernel/prom.c
index f88ce78e13e3..6062e6fa589a 100644
--- a/arch/mips/kernel/prom.c
+++ b/arch/mips/kernel/prom.c
@@ -28,6 +28,8 @@ __init void mips_set_machine_name(const char *name)
strscpy(mips_machine_name, name, sizeof(mips_machine_name));
pr_info("MIPS: machine is %s\n", mips_get_machine_name());
+
+ dump_stack_set_arch_desc(name);
}
char *mips_get_machine_name(void)
--
2.42.1
next prev parent reply other threads:[~2023-11-22 18:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:23 [PATCH 0/7] MIPS: mm: Fix some memory-related issues Serge Semin
2023-11-22 18:23 ` [PATCH 1/7] mips: dmi: Fix early remap on MIPS32 Serge Semin
2023-11-22 19:35 ` Arnd Bergmann
2023-11-23 9:32 ` Serge Semin
2023-11-23 12:13 ` Jiaxun Yang
2023-11-23 12:29 ` Thomas Bogendoerfer
2023-11-23 15:07 ` Jiaxun Yang
2023-11-23 16:07 ` Thomas Bogendoerfer
2023-11-23 17:33 ` Jiaxun Yang
2023-11-24 18:52 ` Serge Semin
2023-11-24 22:03 ` Jiaxun Yang
2023-11-27 16:23 ` Serge Semin
2023-11-27 21:08 ` Jiaxun Yang
2023-11-28 11:34 ` Serge Semin
2023-11-28 15:46 ` Jiaxun Yang
2023-11-30 19:16 ` Serge Semin
2023-12-01 0:13 ` Jiaxun Yang
2023-12-01 14:54 ` Serge Semin
2023-12-01 15:10 ` Jiaxun Yang
2023-12-01 18:26 ` Serge Semin
2023-11-28 12:41 ` Arnd Bergmann
2023-11-28 13:52 ` Serge Semin
2023-11-28 21:59 ` Arnd Bergmann
2023-11-30 19:26 ` Serge Semin
2023-11-24 22:34 ` Jiaxun Yang
2023-11-22 18:24 ` Serge Semin [this message]
2023-11-22 18:29 ` [PATCH 0/7] MIPS: mm: Fix some memory-related issues Andrew Morton
2023-11-23 10:12 ` Serge Semin
[not found] ` <20231122182419.30633-7-fancer.lancer@gmail.com>
2023-11-23 10:06 ` [PATCH 6/7] mm/mm_init.c: Append '\n' to the unavailable ranges log-message Mike Rapoport
[not found] ` <20231122182419.30633-6-fancer.lancer@gmail.com>
2023-11-23 10:18 ` [PATCH 5/7] mm/mm_init.c: Extend init unavailable range doc info Mike Rapoport
[not found] ` <ehlzzv37o4exdn4smmu653wzjdotzdv3dhr3bduvemxssp37ro@sgegnyprquk4>
2023-11-24 8:19 ` Mike Rapoport
[not found] ` <h3g6ynqem6h6hefmdawzaspvzf4u5fwfh7rken3ogy5ucr5z5t@d5gagi2ql4ee>
2023-11-28 7:13 ` Mike Rapoport
[not found] ` <z6r4jvuo63deg5ezzrxiewuzgdfwvcluzp45r4gmu7vwx6fmlm@d5r6phck2ovh>
2023-11-29 6:14 ` Mike Rapoport
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=20231122182419.30633-8-fancer.lancer@gmail.com \
--to=fancer.lancer@gmail.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=akpm@linux-foundation.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=arnd@arndb.de \
--cc=cfu@wavecomp.com \
--cc=dragan.mladjenovic@syrmia.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=willy@infradead.org \
--cc=yangtiezhu@loongson.cn \
--cc=yangyinglu@loongson.cn \
/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).