[Kgdb-bugreport] [PATCH 2/3] proc: Provide access to /proc/interrupts from kdb

[Daniel Thompson]

The contents of /proc/interrupts is useful to diagnose problems during
boot up or when the system becomes unresponsive (or at least it can be if
failure is causes by interrupt problems). This command is also seen in
out-of-tree debug systems such as Android's FIQ debugger.

This change allows the file to be displayed from kdb.

Signed-off-by: Daniel Thompson <daniel.thomp...@linaro.org>
---
 fs/proc/interrupts.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/fs/proc/interrupts.c b/fs/proc/interrupts.c
index a352d57..d8b64f0 100644
--- a/fs/proc/interrupts.c
+++ b/fs/proc/interrupts.c
@@ -4,6 +4,7 @@
 #include <linux/irqnr.h>
 #include <linux/proc_fs.h>
 #include <linux/seq_file.h>
+#include <linux/kdb.h>
 
 /*
  * /proc/interrupts
@@ -45,9 +46,16 @@ static const struct file_operations 
proc_interrupts_operations = {
        .release        = seq_release,
 };
 
+static int kdb_interrupts(int argc, const char **argv)
+{
+       return kdb_print_seq_file(&int_seq_ops);
+}
+
 static int __init proc_interrupts_init(void)
 {
        proc_create("interrupts", 0, NULL, &proc_interrupts_operations);
+       kdb_register("interrupts", kdb_interrupts, "",
+                    "Show /proc/interrupts", 3);
        return 0;
 }
 fs_initcall(proc_interrupts_init);
-- 
1.9.0


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport