Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758951AbYHSUX2 (ORCPT ); Tue, 19 Aug 2008 16:23:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754117AbYHSUXU (ORCPT ); Tue, 19 Aug 2008 16:23:20 -0400 Received: from tomts40.bellnexxia.net ([209.226.175.97]:57856 "EHLO tomts40-srv.bellnexxia.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751107AbYHSUXT (ORCPT ); Tue, 19 Aug 2008 16:23:19 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIEABDEqkhMRKxB/2dsb2JhbACBYrU+gVs Date: Tue, 19 Aug 2008 16:23:16 -0400 From: Mathieu Desnoyers To: Pekka Enberg Cc: Eduard - Gabriel Munteanu , "Randy.Dunlap" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, mpm@selenic.com, tglx@linutronix.de, rostedt@goodmis.org, cl@linux-foundation.org, tzanussi@gmail.com Subject: Re: [PATCH 1/5] Revert "kmemtrace: fix printk format warnings" Message-ID: <20080819202316.GA4188@Krystal> References: <1219167807-5407-1-git-send-email-eduard.munteanu@linux360.ro> <20080819175440.GA5435@localhost> <20080819181652.GA29757@Krystal> <20080819183203.GB5520@localhost> <48AB1E43.2010408@cs.helsinki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <48AB1E43.2010408@cs.helsinki.fi> X-Editor: vi X-Info: http://krystal.dyndns.org:8080 X-Operating-System: Linux/2.6.21.3-grsec (i686) X-Uptime: 16:22:50 up 76 days, 1:03, 7 users, load average: 0.21, 0.87, 1.10 User-Agent: Mutt/1.5.16 (2007-06-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1690 Lines: 44 * Pekka Enberg (penberg@cs.helsinki.fi) wrote: > Eduard - Gabriel Munteanu wrote: >> On Tue, Aug 19, 2008 at 02:16:53PM -0400, Mathieu Desnoyers wrote: >>> Question : >>> >>> Is this kmemtrace marker meant to be exposed to userspace ? >>> >>> I suspect not. In all case, not directly. I expect in-kernel probes to >>> be connected on these markers which will get the arguments they need, >>> and maybe access the inner data structures. Anyhow, tracepoints should >>> be used for that, not markers. You can later put markers in the probes >>> which are themselves connected to tracepoints. >>> >>> Tracepoints = in-kernel tracing API. >>> >>> Markers = Data-formatting tracing API, meant to export the data either >>> to user-space in text or binary format. >>> >>> See >>> >>> http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=shortlog >>> >>> tracepoint-related patches. >> I think we're ready to try tracepoints. Pekka, could you merge Mathieu's >> tracepoints or otherwise provide a branch where I could submit a >> tracepoint conversion patch for kmemtrace? > > Sorry, that's too much of a hassle for me. I'll happily take your > conversion patch once tracepoints hit mainline. Mathieu, are you aiming for > 2.6.28? Probably. it's in -tip right now, and the new ftrace depends on it. So at least 2.6.28 yes. Mathieu -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 -- 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/