[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-57b8015e07a70301e9ec9f324db1a8b73b5a1e2b@git.kernel.org>
Date: Wed, 17 Apr 2013 12:56:04 -0700
From: tip-bot for Pavel Emelyanov <tipbot@...or.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
matt.helsley@...il.com, peterz@...radead.org, xemul@...allels.com,
tglx@...utronix.de, mtk.manpages@...il.com
Subject: [tip:timers/core] posix-timers: Show sigevent info in proc file
Commit-ID: 57b8015e07a70301e9ec9f324db1a8b73b5a1e2b
Gitweb: http://git.kernel.org/tip/57b8015e07a70301e9ec9f324db1a8b73b5a1e2b
Author: Pavel Emelyanov <xemul@...allels.com>
AuthorDate: Mon, 11 Mar 2013 13:13:08 +0400
Committer: Thomas Gleixner <tglx@...utronix.de>
CommitDate: Wed, 17 Apr 2013 20:51:01 +0200
posix-timers: Show sigevent info in proc file
Previous patch added proc file to list posix timers created by task.
Expand the information provided in this file by adding info about
notification method, with which timers were created. I.e. after
the "ID:" line there go
1. "signal:" line, that shows signal number and sigval bits;
2. "notify:" line, that shows the timer notification method.
Thus the timer entry would looke like this:
ID: 123
signal: 14/0000000000b005d0
notify: signal/pid.732
This information is enough to understand how timer_create() was called
for each particular timer.
Signed-off-by: Pavel Emelyanov <xemul@...allels.com>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Michael Kerrisk <mtk.manpages@...il.com>
Cc: Matthew Helsley <matt.helsley@...il.com>
Link: http://lkml.kernel.org/r/513DA024.80404@parallels.com
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
---
fs/proc/base.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 01def9f..a193086 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -2018,6 +2018,7 @@ struct timers_private {
struct pid *pid;
struct task_struct *task;
struct sighand_struct *sighand;
+ struct pid_namespace *ns;
unsigned long flags;
};
@@ -2060,9 +2061,24 @@ static void timers_stop(struct seq_file *m, void *v)
static int show_timer(struct seq_file *m, void *v)
{
struct k_itimer *timer;
+ struct timers_private *tp = m->private;
+ int notify;
+ static char *nstr[] = {
+ [SIGEV_SIGNAL] = "signal",
+ [SIGEV_NONE] = "none",
+ [SIGEV_THREAD] = "thread",
+ };
timer = list_entry((struct list_head *)v, struct k_itimer, list);
+ notify = timer->it_sigev_notify;
+
seq_printf(m, "ID: %d\n", timer->it_id);
+ seq_printf(m, "signal: %d/%p\n", timer->sigq->info.si_signo,
+ timer->sigq->info.si_value.sival_ptr);
+ seq_printf(m, "notify: %s/%s.%d\n",
+ nstr[notify & ~SIGEV_THREAD_ID],
+ (notify & SIGEV_THREAD_ID) ? "tid" : "pid",
+ pid_nr_ns(timer->it_pid, tp->ns));
return 0;
}
@@ -2084,6 +2100,7 @@ static int proc_timers_open(struct inode *inode, struct file *file)
return -ENOMEM;
tp->pid = proc_pid(inode);
+ tp->ns = inode->i_sb->s_fs_info;
return 0;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists