Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757193Ab1DGDTP (ORCPT ); Wed, 6 Apr 2011 23:19:15 -0400 Received: from mail4.hitachi.co.jp ([133.145.228.5]:42901 "EHLO mail4.hitachi.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755441Ab1DGDTN (ORCPT ); Wed, 6 Apr 2011 23:19:13 -0400 X-AuditID: b753bd60-9c7ccba000000f4e-6e-4d9d2d2eeefa X-AuditID: b753bd60-9c7ccba000000f4e-6e-4d9d2d2eeefa Message-ID: <4D9D2D28.4040508@hitachi.com> Date: Thu, 07 Apr 2011 12:19:04 +0900 From: Masami Hiramatsu Organization: Systems Development Lab., Hitachi, Ltd., Japan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Srikar Dronamraju Cc: Peter Zijlstra , Ingo Molnar , Steven Rostedt , Linux-mm , Arnaldo Carvalho de Melo , Linus Torvalds , Ananth N Mavinakayanahalli , Christoph Hellwig , Andi Kleen , Thomas Gleixner , Jonathan Corbet , Oleg Nesterov , Andrew Morton , Jim Keniston , Roland McGrath , SystemTap , LKML Subject: Re: [PATCH v3 2.6.39-rc1-tip 26/26] 26: uprobes: filter chain References: <20110401143223.15455.19844.sendpatchset@localhost6.localdomain6> <20110401143737.15455.30181.sendpatchset@localhost6.localdomain6> <4D9A6FE8.2010301@hitachi.com> <20110406224148.GA5806@linux.vnet.ibm.com> In-Reply-To: <20110406224148.GA5806@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1579 Lines: 47 (2011/04/07 7:41), Srikar Dronamraju wrote: >>> +static bool filter_chain(struct uprobe *uprobe, struct task_struct *t) >>> +{ >>> + struct uprobe_consumer *consumer; >>> + bool ret = false; >>> + >>> + down_read(&uprobe->consumer_rwsem); >>> + for (consumer = uprobe->consumers; consumer; >>> + consumer = consumer->next) { >>> + if (!consumer->filter || consumer->filter(consumer, t)) { >>> + ret = true; >>> + break; >>> + } >>> + } >>> + up_read(&uprobe->consumer_rwsem); >>> + return ret; >>> +} >>> + >> >> Where this function is called from ? This patch seems the last one of this series... >> > > Sorry for the delayed reply, I was travelling to LFCS. > Still I have to connect the filter from trace/perf probe. I see, and I'd like to suggest you to separate that series from this "uprobe" series. For upstream merge, indeed, we need a consumer of the uprobe. However, it should be as simple as possible, so that we can focus on reviewing uprobe itself. > Thats listed as todo and thats the next thing I am planning to work on. Interesting:) Could you tell us what the plan will introduce? How will it be connected? how will we use it? Thank you, -- Masami HIRAMATSU Software Platform Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt@hitachi.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/