From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Shuah Khan <shuah.kh@samsung.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases
Date: Fri, 26 Sep 2014 21:04:26 +0900 [thread overview]
Message-ID: <5425564A.4020107@hitachi.com> (raw)
In-Reply-To: <5422F328.2040707@osg.samsung.com>
(2014/09/25 1:36), Shuah Khan wrote:
> On 09/24/2014 10:30 AM, Steven Rostedt wrote:
>> On Wed, 24 Sep 2014 10:22:12 -0600
>> Shuah Khan <shuahkh@osg.samsung.com> wrote:
>>
>>
>>> One simple approach is to have the user install the required tools
>>> for the test. Indicate what is needed and fail the test with
>>> appropriate message with xskip. This is what I have in mind for
>>> tests that can't be run because of a missing config. The same can
>>> be extended to external tools that the test depends on.
>>
>> Should I hold off adding my tests until we have all this in place. Or
>> should I just push my tests with simply passing if the config isn't
>> supported for now and add it later?
>>
>> I wont add any of the tests that require other tools besides echo, grep
>> and cat.
They are supported by busybox :)
> Please go ahead and get them in. The framework might have to wait
> until 3.19, so there is no need to have it gate test development.
> We can evolve them as we go. If tests require special, it means that
> they aren't suitable for certain envs such as qemu boot with busybox.
> There is a plan to add test targets to cover such cases.
Agreed, anyway, in some env those tools(commands) may not supported
by busybox because of the memory size etc. In that case, we can just
mark the test unsupported or xfail.
Thank you,
> I would recommend at least printing a message saying what you are
> missing if you find something missing.
>
> thanks,
> -- Shuah
>
>
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-09-26 12:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 21:38 [RFC][PATCH] ftracetest: Add a couple of ftrace test cases Steven Rostedt
2014-09-24 2:58 ` Masami Hiramatsu
2014-09-24 15:42 ` Steven Rostedt
2014-09-24 15:58 ` Steven Rostedt
2014-09-24 16:01 ` Shuah Khan
2014-09-24 16:08 ` Steven Rostedt
2014-09-24 16:22 ` Shuah Khan
2014-09-24 16:30 ` Steven Rostedt
2014-09-24 16:36 ` Shuah Khan
2014-09-26 12:04 ` Masami Hiramatsu [this message]
2014-09-26 14:18 ` Steven Rostedt
2014-09-29 10:33 ` Masami Hiramatsu
2014-09-26 6:06 ` Namhyung Kim
2014-09-26 11:54 ` Masami Hiramatsu
2014-09-26 14:46 ` Namhyung Kim
2014-09-29 11:40 ` Masami Hiramatsu
2014-09-30 6:24 ` Namhyung Kim
2014-09-26 14:07 ` Steven Rostedt
2014-09-25 0:35 ` Masami Hiramatsu
2014-09-25 1:14 ` Steven Rostedt
2014-09-25 3:20 ` Masami Hiramatsu
2014-09-25 1:29 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5425564A.4020107@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shuah.kh@samsung.com \
--cc=shuahkh@osg.samsung.com \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).