Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932571AbZKNAai (ORCPT ); Fri, 13 Nov 2009 19:30:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932435AbZKNAah (ORCPT ); Fri, 13 Nov 2009 19:30:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:3814 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932430AbZKNAag (ORCPT ); Fri, 13 Nov 2009 19:30:36 -0500 Message-ID: <4AFDF9DA.6090308@redhat.com> Date: Fri, 13 Nov 2009 19:29:14 -0500 From: Masami Hiramatsu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 MIME-Version: 1.0 To: Roland McGrath CC: Ingo Molnar , lkml , systemtap , DLE Subject: Re: [PATCH -tip 3/3] Add get_signal tracepoint References: <20091113225226.15079.90813.stgit@harusame> <20091113225240.15079.4863.stgit@harusame> <20091113235333.0E3CC15E8@magilla.sf.frob.com> In-Reply-To: <20091113235333.0E3CC15E8@magilla.sf.frob.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1722 Lines: 49 Roland McGrath wrote: > This is orthogonal to the core-dump tracepoint, I don't see why you > call them a unified patch series. Agreed, I'll split them. > The proper name for this event is "signal delivery". But since the > proper name for "send_signal" is "signal generation", I suppose "get" > is analogously improper to the existing "send" tracepoint. ;-) Ah, I see. 'deliver_signal' is good to me :-). Thank you, > Especially if you call this "get" rather than "deliver", there is > another place that should invoke this tracepoint (or perhaps a third > one). sys_rt_sigtimedwait "gets" a signal without delivering it. In > POSIX terminology this is called "accepting" the signal: the three > things that can happen in the life of a signal are "generate", > "deliver", and "accept". If you are trying to match up what happened to > a signal generated by kill() or whatnot, then you want to notice both > delivery and acceptance as the complementary event. > > (And again I have no clue why this signal stuff should be called > "sched" at all.) > > > Thanks, > Roland > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Masami Hiramatsu Software Engineer Hitachi Computer Products (America), Inc. Software Solutions Division e-mail: mhiramat@redhat.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/