From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753607Ab2G3Pva (ORCPT ); Mon, 30 Jul 2012 11:51:30 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:13411 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753018Ab2G3Pv2 (ORCPT ); Mon, 30 Jul 2012 11:51:28 -0400 X-Authority-Analysis: v=2.0 cv=LIjkseq9 c=1 sm=0 a=s5Htg7xnQOKvHEu9STBOug==:17 a=OpT9cpI26MMA:10 a=yskIVUSqD-kA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=meVymXHHAAAA:8 a=ayC55rCoAAAA:8 a=dhFxkLuXi8K1J-75sbsA:9 a=PUjeQqilurYA:10 a=s5Htg7xnQOKvHEu9STBOug==:117 X-Cloudmark-Score: 0 X-Originating-IP: 72.230.195.127 Message-ID: <1343663487.27983.7.camel@gandalf.stny.rr.com> Subject: Re: [PATCH 00/19] [GIT PULL][v3.6] ftrace: Allow kprobes to work with ftace From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Ingo Molnar , Andrew Morton , Masami Hiramatsu , Frederic Weisbecker , Thomas Gleixner , "H. Peter Anvin" Date: Mon, 30 Jul 2012 11:51:27 -0400 In-Reply-To: <20120721021943.274162381@goodmis.org> References: <20120721021943.274162381@goodmis.org> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.4.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2012-07-20 at 22:19 -0400, Steven Rostedt wrote: > Ingo, > > This patch series extends ftrace function tracing utility to be > more dynamic for its users. It allows for data passing to the callback > functions, as well as reading regs as if a breakpoint were to trigger > at function entry. > > The main goal of this patch series was to allow kprobes to use ftrace > as an optimized probe point when a probe is placed on an ftrace nop. > With lots of help from Masami Hiramatsu, and going through lots of > iterations, we finally came up with a good solution. > > I've tested it vigorously (although, like always, there may be some > subtle bug), but I feel it is ready for inclussion for the 3.6 merge > window. As the merge window opened the day after I sent this (which was also the same day I left for vacation :-p ), I recommend that this goes in v3.7. Can you pull this in for 3.7, or do you want me to post another pull request after the merge window closes? Thanks, -- Steve