From: Roland McGrath <roland@redhat.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH -tip 0/3] tracepoint: Add signal events
Date: Wed, 18 Nov 2009 21:19:00 -0000 [thread overview]
Message-ID: <20091118211829.4A2471A8F@magilla.sf.frob.com> (raw)
In-Reply-To: Masami Hiramatsu's message of Wednesday, 18 November 2009 11:32:34 -0500 <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
prev parent reply other threads:[~2009-11-18 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 23:40 Masami Hiramatsu
2009-11-18 0:08 ` [PATCH -tip 1/3] tracepoint: Move signal sending tracepoint to events/signal.h Masami Hiramatsu
2009-11-18 0:11 ` [PATCH -tip 2/3] tracepoint: Add signal deliver event Masami Hiramatsu
2009-11-18 0:53 ` [PATCH -tip 3/3] tracepoint: Add signal loss events Masami Hiramatsu
2009-11-18 3:08 ` [PATCH -tip 0/3] tracepoint: Add signal events Roland McGrath
2009-11-18 16:33 ` Masami Hiramatsu
2009-11-18 21:19 ` Roland McGrath [this message]
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=20091118211829.4A2471A8F@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).