From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: Warning from ring buffer code (Was: Re: linux-next: tip tree build warning) Date: Mon, 14 Sep 2009 20:23:41 +0200 Message-ID: <1252952621.31964.0.camel@twins> References: <20090804161640.70817ee6.sfr@canb.auug.org.au> <1249403089.4634.139.camel@localhost.localdomain> <20090912165300.9d257283.sfr@canb.auug.org.au> <20090912073906.GA3972@elte.hu> <1252753957.12217.10.camel@ht.satnam> <1252941416.2964.143.camel@localhost.localdomain> <70318cbf0909141009v46581785m4c70edf31fcb79fa@mail.gmail.com> <1252952238.2964.154.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1252952238.2964.154.camel@localhost.localdomain> Sender: linux-next-owner@vger.kernel.org To: Steven Rostedt Cc: Christopher Li , Jaswinder Singh Rajput , Ingo Molnar , Stephen Rothwell , Thomas Gleixner , "H. Peter Anvin" , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sparse@vger.kernel.org, Josh Triplett , Frederic Weisbecker List-Id: linux-sparse@vger.kernel.org On Mon, 2009-09-14 at 14:17 -0400, Steven Rostedt wrote: > Frederic, how big can one of those events get. The ring buffer (and > TRACE_EVENT) allow up to almost a page size, which is very hefty for the > stack. This code needs to either be rewritten or we need to set a limit > to the size of a profile entry. Yeah, that needs to get a re-write.. I've complained about this when it went in.