linux-kernel - Re: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1411742793.1669.14.camel@leonhard>
Date:	Fri, 26 Sep 2014 23:46:33 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Shuah Khan <shuahkh@....samsung.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Shuah Khan <shuah.kh@...sung.com>,
	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases

Hi Masami,

2014-09-26 (금), 20:54 +0900, Masami Hiramatsu:
> (2014/09/26 15:06), Namhyung Kim wrote:
> > Hi Steve,
> > 
> > On Wed, 24 Sep 2014 12:08:53 -0400, Steven Rostedt wrote:
> >> On Wed, 24 Sep 2014 10:01:38 -0600
> >> Shuah Khan <shuahkh@....samsung.com> wrote:
> >>
> >>> I am working on adding the framework for c tests. We will have
> >>> to get this evolved for shell scripts. Please see the following
> >>> thread:
> >>>
> >>> https://lkml.org/lkml/2014/9/23/926
> >>>
> >>
> >> Thanks,
> >>
> >> Also, what's the rules for a test that requires other tools. Some of my
> >> tests require trace-cmd to be installed as well as perf. My stress test
> >> runs perf against trace-cmd running hackbench (another required tool),
> >> but I believe that perf has hackbench built in so I could replace
> >> hackbench with the perf version.
> > 
> > Yeah, and I think we can at least build perf (if not found) for test as
> > we can always have the source.  The trace-cmd is different and it'd be
> > another reason I need to work on 'perf ftrace' command soon.  ;-)
> 
> +1 :)
> 
> For the kselftest, we can only expect to have tools in kernel tree (which
> should be static-linked) and busybox, so that we can use qemu emulator to
> run kselftest on other archs. I guess perf still need some shared
> objects to run. That should be solved too.

The perf should be built with no extra dependencies (other than libc).
It won't provide rich features but basic functionality (record, report,
stat) should be supported.  And I'm also thinking about implementing a
very simple elf parser for symbol loading in such a minimal build.

Thanks,
Namhyung


> 
> Anyway, at first we'd better add simpler tests which is not relay on
> other tools except busybox shell.
> 
> Thank you,
> 
> 



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/