From: "Björn Töpel" <bjorn@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org
Cc: "Björn Töpel" <bjorn@rivosinc.com>,
"Andreas Schwab" <schwab@linux-m68k.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler
Date: Thu, 19 Jan 2023 08:47:36 +0100 [thread overview]
Message-ID: <20230119074738.708301-1-bjorn@kernel.org> (raw)
From: Björn Töpel <bjorn@rivosinc.com>
RISC-V does not dump faulting instructions in the oops handler. This
series adds "Code:" dumps to the oops output together with
scripts/decodecode support.
Thanks,
Björn
v2->v3: Simplifications/getting rid of casts (Geert)
v1->v2: Dump instructions in 16b parcels (Andreas)
Björn Töpel (2):
riscv: Add instruction dump to RISC-V splats
scripts/decodecode: Add support for RISC-V
arch/riscv/kernel/traps.c | 25 ++++++++++++++++++++++++-
scripts/decodecode | 12 +++++++++++-
2 files changed, 35 insertions(+), 2 deletions(-)
base-commit: 7287904c8771b77b9504f53623bb477065c19a58
--
2.37.2
next reply other threads:[~2023-01-20 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 7:47 Björn Töpel [this message]
2023-01-19 7:47 ` [PATCH v3 1/2] riscv: Add instruction dump to RISC-V splats Björn Töpel
2023-01-19 7:47 ` [PATCH v3 2/2] scripts/decodecode: Add support for RISC-V Björn Töpel
2023-02-21 15:18 ` Alexandre Ghiti
2023-02-22 15:00 ` [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler patchwork-bot+linux-riscv
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=20230119074738.708301-1-bjorn@kernel.org \
--to=bjorn@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@linux-m68k.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