From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756992AbbEVM3F (ORCPT <rfc822;w@1wt.eu>);
	Fri, 22 May 2015 08:29:05 -0400
Received: from mail-wi0-f170.google.com ([209.85.212.170]:32908 "EHLO
	mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756006AbbEVM3C (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 22 May 2015 08:29:02 -0400
Message-ID: <555F2109.3080306@monom.org>
Date: Fri, 22 May 2015 14:28:57 +0200
From: Daniel Wagner <wagi@monom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
CC: Ingo Molnar <mingo@kernel.org>, Andrew Morton <akpm@linux-foundation.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Namhyung Kim <namhyung@kernel.org>,
        Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Jiri Olsa <jolsa@kernel.org>
Subject: Re: [RFC][PATCH 00/19] tracing: Remove "ftrace" from TRACE_EVENT
 files
References: <20150514151315.746637810@goodmis.org>
In-Reply-To: <20150514151315.746637810@goodmis.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Steven,

On 05/14/2015 05:13 PM, Steven Rostedt wrote:
> Although the name "ftrace" is used to describe the kernel tracing
> infrastructure, in actuality it is really just the function hook
> infrastructure. The TRACE_EVENT system is more generic and is used
> by tracing, perf and lttng as well as others.
> 
> This gets confusing at times, as it is not consistent in the naming.
> The kernel should only use "ftrace" when describing the function hook
> infrastructure. For trace_events and recording, it really should just
> use "trace".
> 
> This only changes the internal infrastructure code and to make sure
> such a large change has no impact, I tested it by merging this branch
> into linux-next and building an allmodconfig. There were no build
> failures or warnings due to this change set.
> 
> I plan on doing further testing and hopefully get this ready for 4.2.
> When my testing is complete, I'll be pushing this into linux-next.

I compiled each patch individually and did some smoke testing. No
problems found so far. I don't know if that already classifies for the
Tested-by tag, though feel free adding it.

cheers,
daniel