Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934244AbZKXV2q (ORCPT ); Tue, 24 Nov 2009 16:28:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934071AbZKXV2p (ORCPT ); Tue, 24 Nov 2009 16:28:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:10330 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934038AbZKXV2p (ORCPT ); Tue, 24 Nov 2009 16:28:45 -0500 Date: Tue, 24 Nov 2009 22:22:47 +0100 From: Oleg Nesterov To: Ingo Molnar Cc: Masami Hiramatsu , lkml , Roland McGrath , Jason Baron , systemtap , DLE Subject: Re: [PATCH -tip v3 0/3] tracepoint: Add signal events Message-ID: <20091124212247.GA11773@redhat.com> References: <20091120213108.14708.97871.stgit@dhcp-100-2-132.bos.redhat.com> <20091123175740.GA15594@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091123175740.GA15594@elte.hu> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2131 Lines: 61 On 11/23, Ingo Molnar wrote: > > * Masami Hiramatsu wrote: > > > Hi, > > > > These patches add signal related tracepoints including > > signal generation, delivery, and loss. First patch also > > moves signal-sending tracepoint from events/sched.h to > > events/signal.h. > > > > Changes in v3 > > - Add Docbook style comments > > > > Changes in v2 > > - Add siginfo arguments > > > > Thank you, > > > > --- > > > > Masami Hiramatsu (3): > > tracepoint: Add signal loss events > > tracepoint: Add signal deliver event > > tracepoint: Move signal sending tracepoint to events/signal.h > > > > > > Documentation/DocBook/tracepoint.tmpl | 5 + > > include/trace/events/sched.h | 25 ----- > > include/trace/events/signal.h | 173 +++++++++++++++++++++++++++++++++ > > kernel/signal.c | 27 ++++- > > 4 files changed, 198 insertions(+), 32 deletions(-) > > create mode 100644 include/trace/events/signal.h > > Would be nice to have Roland's and Oleg's Acked-by tags in the patches - > to show that this is a representative and useful looking set of signal > events. Sorry, I can't really comment these patches. I mean, I do not know which info is useful and which is not. For example, I am a bit surprized we report trace_signal_lose_info() but please do not consider this as if I think we shouldn't. Just I do not know. OTOH, we do not report if __send_signal() fails just because the legacy signal is already queued. We do not report who sends the signal, we do not report if it was private or shared. zap_process, complete_signal can "send" SIGKILL via sigaddset, this won't be noticed. But again, it is not that I think this should be reported. In short: I think any info may be useful, and these patches can help. But I do not understand what exactly should be reported to userspace. Oleg. -- 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/