Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752728AbbFHP5H (ORCPT ); Mon, 8 Jun 2015 11:57:07 -0400 Received: from verein.lst.de ([213.95.11.211]:43515 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751570AbbFHP5D (ORCPT ); Mon, 8 Jun 2015 11:57:03 -0400 Date: Mon, 8 Jun 2015 17:57:01 +0200 From: Torsten Duwe To: Steven Rostedt Cc: Michael Ellerman , ppc-dev , Jiri Kosina , Linux Kernel Mailing List Subject: Re: [PATCH 1/4] ppc64 ftrace implementation Message-ID: <20150608155701.GA23784@lst.de> References: <20150513161100.GA1619@lst.de> <1431653687.13498.1.camel@ellerman.id.au> <20150515084542.GA20453@suse.de> <20150516080534.GA27059@lst.de> <1432006027.8339.3.camel@ellerman.id.au> <20150603130257.GA19424@lst.de> <20150603130829.GB19424@lst.de> <20150608113032.07544ece@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150608113032.07544ece@gandalf.local.home> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 926 Lines: 29 On Mon, Jun 08, 2015 at 11:30:32AM -0400, Steven Rostedt wrote: > > Why are your patches all as replies? Because I cared too much about the threading and the series that the "Re:" escaped me. > > Implement ftrace on ppc64 > > What do you mean "Implement ftrace on ppc64"? It's already implemented. Sorry, too deep in the details. It's DYNAMIC_FTRACE_WITH_REGS, actually. Using gcc's -mprofile-kernel to call into ftrace... > I'm not even going to bother looking at this patch because I have no > idea what its purpose is. Understandable ;-) So: Implement DYNAMIC_FTRACE_WITH_REGS, in order to prepare for live patching. Other obvious things I forgot to mention? Torsten -- 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/