From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752424AbYI3DHe (ORCPT ); Mon, 29 Sep 2008 23:07:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751682AbYI3DGz (ORCPT ); Mon, 29 Sep 2008 23:06:55 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:51355 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751563AbYI3DGy (ORCPT ); Mon, 29 Sep 2008 23:06:54 -0400 Message-Id: <20080930030236.230994826@goodmis.org> User-Agent: quilt/0.46-1 Date: Mon, 29 Sep 2008 23:02:36 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds , Mathieu Desnoyers Subject: [PATCH 0/6] ftrace: port to the new ring_buffer Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org These patches are against linux-tip. The first is just a fix in the wakeup selftest. The next is a port of the Unified tracer buffer to linux-tip and some updates. After that is the ftrace port to use the ring buffer, followed by some more enhancements to ftrace because of the new variable length buffer. I tried a few configurations and tried to test all the different ftrace tracers, but I'm sure there may be some bugs still to work out. I worked out all those that I found. But, with the ring_buffer I can envision several ways to clean up ftrace and to make adding new tracers cleaner. I'm also thinking about making a way that each tracer can allocate its own buffer, and allow for more than one tracer to be running at the same time! (only with different buffers). -- Steve