[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200508161152.5815fd2fac26c300d836f0f1@kernel.org>
Date: Fri, 8 May 2020 16:11:52 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: "Zanussi, Tom" <tom.zanussi@...ux.intel.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Shuah Khan <shuah@...nel.org>, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, Li Philip <philip.li@...el.com>,
Liu Yiding <yidingx.liu@...el.com>
Subject: Re: [PATCH 3/3] selftests/ftrace: Use /bin/echo instead of built-in
echo
On Thu, 7 May 2020 15:32:46 -0500
"Zanussi, Tom" <tom.zanussi@...ux.intel.com> wrote:
> Hi,
>
> On 5/7/2020 12:25 PM, Steven Rostedt wrote:
> > On Fri, 8 May 2020 00:50:28 +0900
> > Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> >>>> Yes, I need Tom's review for this change. As far as I can test, this
> >>>> fixes the test failure. If this isn't acceptable, we can use "alias echo=echo"
> >>>> for this test case.
> >>>>
> >>>
> >>> I still don't see how changing "keys=common_pid" to "keys=ip" has anything
> >>> to do with the echo patch. If that is a problem, it should be a different
> >>> patch with explanation to why "keys=common_pid" is broken.
> >>
> >> This test case uses a trace_marker event to make a histogram with
> >> the common_pid key, and it expects the "echo" command is built-in command
> >> so that the pid is same while writing several events to trace_marker.
> >> I changed it to "ip" which is always same if trace_marker interface is
> >> used.
> >
> > Can you explicitly state that in your change log? It wasn't obvious from
> > what you meant with:
> >
> > "This also fixes some test cases which expects built-in echo command."
OK, will add the description.
> >
>
> With that change,
>
> Reviewed-by: Tom Zanussi <tom.zanussi@...ux.intel.com>
Thanks Tom!
>
> Thanks,
>
> Tom
>
> > Thanks!
> >
> > -- Steve
> >
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists