From: Zhen Lei <thunder.leizhen@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>, James Morse <james.morse@arm.com>
Subject: [PATCH v2] arm64: add the printing of tpidr_elx in __show_regs()
Date: Wed, 16 Mar 2022 14:24:08 +0800 [thread overview]
Message-ID: <20220316062408.1113-1-thunder.leizhen@huawei.com> (raw)
Commit 7158627686f0 ("arm64: percpu: implement optimised pcpu access
using tpidr_el1") and commit 6d99b68933fb ("arm64: alternatives: use
tpidr_el2 on VHE hosts") use tpidr_elx to cache my_cpu_offset to optimize
pcpu access. However, when performing reverse execution based on the
registers and the memory contents in kdump, this information is sometimes
required if there is a pcpu access.
Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
---
arch/arm64/kernel/process.c | 11 +++++++++++
1 file changed, 11 insertions(+)
v1 --> v2:
Directly print the tpidr_elx register of the current exception level.
Avoid coupling with the implementation of 'my_cpu_offset'.
diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
index 5369e649fa79ff8..738932e6fa4e947 100644
--- a/arch/arm64/kernel/process.c
+++ b/arch/arm64/kernel/process.c
@@ -216,6 +216,17 @@ void __show_regs(struct pt_regs *regs)
show_regs_print_info(KERN_DEFAULT);
print_pstate(regs);
+ switch (read_sysreg(CurrentEL)) {
+ case CurrentEL_EL1:
+ printk("tpidr_el1 : %016llx\n", read_sysreg(TPIDR_EL1));
+ break;
+ case CurrentEL_EL2:
+ printk("tpidr_el2 : %016llx\n", read_sysreg(TPIDR_EL2));
+ break;
+ default:
+ break;
+ }
+
if (!user_mode(regs)) {
printk("pc : %pS\n", (void *)regs->pc);
printk("lr : %pS\n", (void *)ptrauth_strip_insn_pac(lr));
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-03-16 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 6:24 Zhen Lei [this message]
2022-04-27 18:40 ` [PATCH v2] arm64: add the printing of tpidr_elx in __show_regs() Catalin Marinas
2022-04-28 10:23 ` Will Deacon
2022-04-28 10:21 ` Will Deacon
2022-04-28 11:07 ` Leizhen (ThunderTown)
2022-04-28 12:03 ` Leizhen (ThunderTown)
2022-04-28 12:10 ` Leizhen (ThunderTown)
2022-04-28 13:13 ` Will Deacon
2022-04-29 4:16 ` Leizhen (ThunderTown)
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=20220316062408.1113-1-thunder.leizhen@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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