Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755317AbYAWSwD (ORCPT ); Wed, 23 Jan 2008 13:52:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756814AbYAWSvv (ORCPT ); Wed, 23 Jan 2008 13:51:51 -0500 Received: from gateway-1237.mvista.com ([63.81.120.158]:17096 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754085AbYAWSvu (ORCPT ); Wed, 23 Jan 2008 13:51:50 -0500 Subject: Re: [PATCH 01/20 -v5] printk - dont wakeup klogd with interrupts disabled From: Daniel Walker To: Steven Rostedt Cc: LKML , Ingo Molnar , Linus Torvalds , Andrew Morton , Peter Zijlstra , Christoph Hellwig , Mathieu Desnoyers , Gregory Haskins , Arnaldo Carvalho de Melo , Thomas Gleixner , Tim Bird , Sam Ravnborg , "Frank Ch. Eigler" , Jan Kiszka , John Stultz , Arjan van de Ven , Steven Rostedt In-Reply-To: References: <20080123160236.969334052@goodmis.org> <20080123160441.236562634@goodmis.org> <1201107978.13596.16.camel@imap.mvista.com> <1201110185.13596.22.camel@imap.mvista.com> <1201112899.13596.25.camel@imap.mvista.com> Content-Type: text/plain Date: Wed, 23 Jan 2008 10:50:12 -0800 Message-Id: <1201114213.13596.29.camel@imap.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.2 (2.12.2-3.fc8) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1449 Lines: 44 On Wed, 2008-01-23 at 13:43 -0500, Steven Rostedt wrote: > On Wed, 23 Jan 2008, Daniel Walker wrote: > > > > > On Wed, 2008-01-23 at 13:18 -0500, Steven Rostedt wrote: > > > > > The wakeup hook in schedule is when we find out that we hit our max. I > > > could postpone that somehow, but that would require more glue code than I > > > would like to add. > > > > Which hook specifically ? > > The wakeup tracer does a print on max when the new task is about to be > switched to (in context_switch). You can't move that hook to when the task actually starts running (i.e. at the end of schedule() ).. > > > > > As for -rt, we've disabled printk for consoles not ATOMIC safe. So the > > > only consoles that will print in atomic sections so far are, earlyprintk > > > and the VGA. > > > > Is this code you added recently for tracing? > > Nope, it's been there for a few releases and had nothing to do with the > latency tracer. > > > > Hmm, seems that only the "hack" fix is in upstream. The Red Hat version > has the better fix, but mainline didn't get it. OK, I'll add that to the > next -rt release. mainline ? The problem I'm thinking of was directly tracing related.. Daniel -- 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/