From: Masami Hiramatsu <mhiramat@redhat.com>
To: Roland McGrath <roland@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 11:32:34 -0500 [thread overview]
Message-ID: <4B0421A2.1080400@redhat.com> (raw)
In-Reply-To: <20091118030706.EB93EA8C@magilla.sf.frob.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.
> In 2/3 this comment:
>
> + /* Trace the actual delivered signals including SIG_IGN.*/
>
> might be slightly misleading. In most cases SIG_IGN signals won't make it
> this far. The same is true of SIG_DFL signals whose default action is to
> ignore. So one should be clear that trace_signal_deliver() is by no means
> expected to get all SIG_IGN signals that are otherwise eligible for delivery.
Ah, thank you for noticing. I'll remove the last words.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-11-18 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 23:41 [PATCH -tip 0/3] tracepoint: Add signal events Masami Hiramatsu
2009-11-17 23:41 ` [PATCH -tip 1/3] tracepoint: Move signal sending tracepoint to events/signal.h Masami Hiramatsu
2009-11-17 23:41 ` [PATCH -tip 2/3] tracepoint: Add signal deliver event Masami Hiramatsu
2009-11-17 23:42 ` [PATCH -tip 3/3] tracepoint: Add signal loss events Masami Hiramatsu
2009-11-18 3:07 ` [PATCH -tip 0/3] tracepoint: Add signal events Roland McGrath
2009-11-18 16:32 ` Masami Hiramatsu [this message]
2009-11-18 21:18 ` Roland McGrath
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=4B0421A2.1080400@redhat.com \
--to=mhiramat@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.