From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755618AbZBWSKA (ORCPT ); Mon, 23 Feb 2009 13:10:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753234AbZBWSJv (ORCPT ); Mon, 23 Feb 2009 13:09:51 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:39167 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753118AbZBWSJu (ORCPT ); Mon, 23 Feb 2009 13:09:50 -0500 Date: Mon, 23 Feb 2009 19:09:41 +0100 From: Ingo Molnar To: Steven Rostedt Cc: Peter Zijlstra , Frederic Weisbecker , LKML , Arnaldo Carvalho de Melo Subject: Re: [PATCH] tracing/ftrace: add missing wake-up on some callsites Message-ID: <20090223180941.GA6015@elte.hu> References: <49a1cc8f.2283420a.54d2.ffff8461@mx.google.com> <20090223162630.GG5961@nowhere> <20090223170528.GH5961@nowhere> <20090223173714.GA601@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > On Mon, 23 Feb 2009, Ingo Molnar wrote: > > > * Steven Rostedt wrote: > > > > > > Which would send a delayed work to wake up? > > > > > > No, I was thinking that trace_delay_wake_up() would be > > > called by these dangerous call sites. Then a per_cpu flag > > > could be set. We could have a trace point in the scheduler > > > code that is outside holding a runqueue lock, and this > > > trace point would call a trace function that will clear > > > the per cpu flag, and then call trace_wake_up(). > > > > No, that's very roundabout and ugly. If we putting a > > tracepoint there we might as well put real scheduler code > > there that looks for such a flag. But i'm not convinced we > > need a flag ... > > Just a suggestion. I was trying to keep the tracer from being > an overhead. But what else would you suggest? Just having the > scheduler call trace_wakeup? i think we could use a TIF flag to trigger a wakeup at the return-to-userspace (or return-from-IRQ) stage or so? Ingo