Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757918Ab0GNXkx (ORCPT ); Wed, 14 Jul 2010 19:40:53 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:59803 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757743Ab0GNXkw (ORCPT ); Wed, 14 Jul 2010 19:40:52 -0400 X-Authority-Analysis: v=1.1 cv=g9Y3NohClm0xo0Au7hiKM/lwvZwqTqjWC8eysRFNA3U= c=1 sm=0 a=ZI5MULQygNwA:10 a=ood2b7iyd8MA:10 a=IkcTkHD0fZMA:10 a=gMqfjgEr1zLu/65IO0LwxA==:17 a=Mg6adXEl9tgf5WbaUv4A:9 a=1eGiirTedtfo6eVo-0gA:7 a=m4yAjOr8uqzNIkJ87n1DXUDuaiQA:4 a=QEXdDO2ut3YA:10 a=gMqfjgEr1zLu/65IO0LwxA==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.89.75 Subject: Re: [patch 1/2] x86_64 page fault NMI-safe From: Steven Rostedt To: Mathieu Desnoyers Cc: Frederic Weisbecker , Linus Torvalds , Ingo Molnar , LKML , Andrew Morton , Peter Zijlstra , Thomas Gleixner , Christoph Hellwig , Li Zefan , Lai Jiangshan , Johannes Berg , Masami Hiramatsu , Arnaldo Carvalho de Melo , Tom Zanussi , KOSAKI Motohiro , Andi Kleen , "H. Peter Anvin" , Jeremy Fitzhardinge , "Frank Ch. Eigler" , Tejun Heo In-Reply-To: <20100714231117.GA22341@Krystal> References: <20100714170617.GB4955@Krystal> <20100714184642.GA9728@elte.hu> <20100714193652.GA13630@nowhere> <20100714221418.GA14533@nowhere> <20100714223107.GA2350@Krystal> <20100714224853.GC14533@nowhere> <20100714231117.GA22341@Krystal> Content-Type: text/plain; charset="UTF-8" Date: Wed, 14 Jul 2010 19:40:44 -0400 Message-ID: <1279150844.4190.29.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 29 [ /me removes the duplicate email of himself! ] On Wed, 2010-07-14 at 19:11 -0400, Mathieu Desnoyers wrote: > > > > So, when an event triggers in perf, we sometimes want to capture the stacktrace > > that led to the event. > > > > We want this stacktrace (here we call that a callchain) to be recorded > > locklessly. So we want this callchain buffer per cpu, with the following > > type: > > Ah OK, so you mean that perf now has 2 different ring buffer implementations ? > How about using a single one that is generic enough to handle perf and ftrace > needs instead ? > > (/me runs away quickly before the lightning strikes) ;) > To be fair, that's just a temp buffer. -- Steve (/me sends this to try to remove the dup email he's getting ) -- 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/