From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
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: Mon, 29 Sep 2014 19:33:22 +0900 [thread overview]
Message-ID: <54293572.9010108@hitachi.com> (raw)
In-Reply-To: <20140926101840.7d495620@gandalf.local.home>
(2014/09/26 23:18), Steven Rostedt wrote:
> On Fri, 26 Sep 2014 21:04:26 +0900
> Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
>
>
>>> 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.
>>
>
> Note, if memory size is such a big issue it that other tools may not be
> there, then most of the ftrace features will probably be disabled due
> to memory constraints on the kernel itself.
Agreed :)
>
> As we have a way to state "unsupported" we can just return that from
> tests that require tools not available, and say why it is the case.
OK, if we can count "unsupported" as a test failure (yes, it is
unexpectedly failed), it is easy to fix. I'll update XFAIL and
other error code support patch and send it.
Thank you,
--
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-29 10:33 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
2014-09-26 14:18 ` Steven Rostedt
2014-09-29 10:33 ` Masami Hiramatsu [this message]
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=54293572.9010108@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.