This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH -tip 0/3] tracepoint: Add signal events

From: Roland McGrath <roland at redhat dot com>
To: Masami Hiramatsu <mhiramat at redhat dot com>
Cc: Ingo Molnar <mingo at elte dot hu>, lkml <linux-kernel at vger dot kernel dot org>, Oleg Nesterov <oleg at redhat dot com>, systemtap <systemtap at sources dot redhat dot com>, DLE <dle-develop at lists dot sourceforge dot net>
Date: Wed, 18 Nov 2009 13:18:29 -0800 (PST)
Subject: Re: [PATCH -tip 0/3] tracepoint: Add signal events
References: <20091117234117.30589.61311.stgit@dhcp-100-2-132.bos.redhat.com> <20091118030706.EB93EA8C@magilla.sf.frob.com> <4B0421A2.1080400@redhat.com>

> Roland McGrath wrote:
> > I would add the siginfo_t * argument to each of these tracepoints.
> 
> I see. Is it OK to record only si_errno and si_code? because si_signo
> might be as same as sig.

Yes, si_signo will match sig.  Which siginfo_t fields are interesting to
record can vary by signal (i.e. by si_code).  si_code and si_errno are
certainly the first things that come to mind as most useful.  For SI_TIMER,
si_tid, si_overrun, and si_sigval are interesting.  For others, si_pid and
si_uid are interesting.

Thanks,
Roland

References:
- [PATCH -tip 0/3] tracepoint: Add signal events
  - From: Masami Hiramatsu
- Re: [PATCH -tip 0/3] tracepoint: Add signal events
  - From: Roland McGrath
- Re: [PATCH -tip 0/3] tracepoint: Add signal events
  - From: Masami Hiramatsu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]