From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: crash-utility@redhat.com, mick@ics.forth.gr,
heinrich.schuchardt@canonical.com, guoren@kernel.org,
k-hagio-ab@nec.com, yixun.lan@gmail.com, lijiang@redhat.com
Cc: linux-riscv@lists.infradead.org, kexec@lists.infradead.org,
hschauhan@nulltrace.org, lifang_xia@linux.alibaba.com,
Xianting Tian <xianting.tian@linux.alibaba.com>
Subject: [Crash-utility][PATCH V4 4/9] RISCV64: Add irq command support
Date: Thu, 20 Oct 2022 09:50:09 +0800 [thread overview]
Message-ID: <20221020015014.46085-5-xianting.tian@linux.alibaba.com> (raw)
In-Reply-To: <20221020015014.46085-1-xianting.tian@linux.alibaba.com>
With the patch, we can get the irq info,
crash> irq
IRQ IRQ_DESC/_DATA IRQACTION NAME
0 (unused) (unused)
1 ff60000001329600 ff60000001d17180 "101000.rtc"
2 ff60000001329800 ff60000001d17680 "ttyS0"
3 ff60000001329a00 ff60000001c33c00 "virtio0"
4 ff60000001329c00 ff60000001c33f80 "virtio1"
5 ff6000000120f400 ff60000001216000 "riscv-timer"
Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
---
riscv64.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/riscv64.c b/riscv64.c
index a137232..3a290ce 100644
--- a/riscv64.c
+++ b/riscv64.c
@@ -989,6 +989,7 @@ riscv64_init(int when)
machdep->get_smp_cpus = riscv64_get_smp_cpus;
machdep->value_to_symbol = generic_machdep_value_to_symbol;
machdep->dis_filter = generic_dis_filter;
+ machdep->dump_irq = generic_dump_irq;
machdep->show_interrupts = generic_show_interrupts;
machdep->get_irq_affinity = generic_get_irq_affinity;
machdep->init_kernel_pgd = NULL; /* pgd set by symbol_value("swapper_pg_dir") */
--
2.17.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-10-20 3:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:50 [Crash-utility][PATCH V4 0/9] Support RISCV64 arch and common commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 1/9] Add RISCV64 framework code support Xianting Tian
2022-10-21 2:17 ` HAGIO KAZUHITO(萩尾 一仁)
2022-10-21 2:42 ` Xianting Tian
2022-10-21 2:57 ` HAGIO KAZUHITO(萩尾 一仁)
2022-11-03 5:32 ` lijiang
2022-11-09 9:01 ` Xianting Tian
2022-12-22 4:48 ` HAGIO KAZUHITO(萩尾 一仁)
2022-10-20 1:50 ` [Crash-utility][PATCH V4 2/9] RISCV64: Make crash tool enter command line and support some commands Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 3/9] RISCV64: Add 'dis' command support Xianting Tian
2022-10-20 1:50 ` Xianting Tian [this message]
2022-10-20 1:50 ` [Crash-utility][PATCH V4 5/9] RISCV64: Add 'bt' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 6/9] RISCV64: Add 'help -r' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 7/9] RISCV64: Add 'help -m/M' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 8/9] RISCV64: Add 'mach' " Xianting Tian
2022-10-20 1:50 ` [Crash-utility][PATCH V4 9/9] RISCV64: Add the implementation of symbol verify Xianting Tian
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=20221020015014.46085-5-xianting.tian@linux.alibaba.com \
--to=xianting.tian@linux.alibaba.com \
--cc=crash-utility@redhat.com \
--cc=guoren@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=lifang_xia@linux.alibaba.com \
--cc=lijiang@redhat.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=yixun.lan@gmail.com \
/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