[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201008033440.zpk2afmgvs5aruq2@master>
Date: Thu, 8 Oct 2020 03:34:40 +0000
From: Wei Yang <richard.weiyang@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Wei Yang <richard.weiyang@...ux.alibaba.com>, mingo@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] ftrace: replace do_for_each_ftrace_rec() with
for_ftrace_rec_iter()
On Tue, Oct 06, 2020 at 10:42:17AM -0400, Steven Rostedt wrote:
>On Mon, 31 Aug 2020 11:11:03 +0800
>Wei Yang <richard.weiyang@...ux.alibaba.com> wrote:
>
>> Now we have two similar infrastructure to iterate ftrace_page and
>> dyn_ftrace:
>>
>> * do_for_each_ftrace_rec()
>> * for_ftrace_rec_iter()
>>
>> The 2nd one, for_ftrace_rec_iter(), looks more generic, so preserve it
>> and replace do_for_each_ftrace_rec() with it.
>>
>
>I also didn't pull in this patch. The reason is that the
>for_ftrace_rec_iter() is specific for external usage (for archs to use) and
>requires two function calls to do the iterations.
>
>The do_for_each_ftrace_rec() is a faster, light weight version, but for
>internal use only.
>
>I rather keep both, as each has their own, but slightly different, use
>cases.
>
Got it, thanks
>-- Steve
--
Wei Yang
Help you, Help me
Powered by blists - more mailing lists