Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752336AbdHNSoT (ORCPT ); Mon, 14 Aug 2017 14:44:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42518 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751807AbdHNSoS (ORCPT ); Mon, 14 Aug 2017 14:44:18 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com BCE9F883BC Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mpetlan@redhat.com Date: Mon, 14 Aug 2017 20:44:14 +0200 (CEST) From: Michael Petlan X-X-Sender: Michael@Diego To: tmricht@linux.vnet.ibm.com, namhyung@kernel.org, dsahern@gmail.com, jolsa@kernel.org, tglx@linutronix.de, hpa@zytor.com, mingo@kernel.org, adrian.hunter@intel.com, wangnan0@huawei.com, acme@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [tip:perf/core] perf test shell: Install shell tests In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Mon, 14 Aug 2017 18:44:18 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4574 Lines: 98 Hi Arnaldo! Maybe this would be the right time to incorporate the shell-based perftool-testsuite [1] into perf-test, wouldn't it? It already contains bunch of shell-based perf tests that cover 25+ RH bugs... A little problem might be different design, since the testsuite has multiple levels of hierarchy of sub-sub-sub-tests, like: ... -- [ PASS ] -- perf_probe :: test_probe_syntax :: custom named probe :: add -- [ PASS ] -- perf_probe :: test_probe_syntax :: custom named probe :: list -- [ PASS ] -- perf_probe :: test_probe_syntax :: custom named probe :: use -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: vfs_read@fs/read_write.c -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: vfs_read:11@fs/read_write.c -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: vfs_read@fs/read_write.c:11 -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: vfs_read%return -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: test.c:29 -- [ PASS ] -- perf_probe :: test_probe_syntax :: various syntax forms :: func%return $retval ## [ PASS ] ## perf_probe :: test_probe_syntax SUMMARY -- [ PASS ] -- perf_probe :: test_sdt :: adding SDT tracepoints as probes -- [ PASS ] -- perf_probe :: test_sdt :: listing added probes -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf stat (N = 13) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf stat (N = 128) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf stat (N = 241) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf record (N = 37) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf report (N = 37) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf script (N = 37) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf record (N = 97) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf report (N = 97) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf script (N = 97) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf record (N = 237) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf report (N = 237) -- [ PASS ] -- perf_probe :: test_sdt :: using probes :: perf script (N = 237) ## [ PASS ] ## perf_probe :: test_sdt SUMMARY ... ... which does not exactly match how perf-test is structured, however, I think that the multi-level structure of the testsuite is important for keeping some order in it... What do you think? Cheers, Michael [1] https://github.com/rfmvh/perftool-testsuite On Mon, 14 Aug 2017, tip-bot for Arnaldo Carvalho de Melo wrote: > Commit-ID: 122e0b947052f6106595fa29d63d514d2ebcdad9 > Gitweb: http://git.kernel.org/tip/122e0b947052f6106595fa29d63d514d2ebcdad9 > Author: Arnaldo Carvalho de Melo > AuthorDate: Fri, 4 Aug 2017 12:19:44 -0300 > Committer: Arnaldo Carvalho de Melo > CommitDate: Fri, 11 Aug 2017 16:06:28 -0300 > > perf test shell: Install shell tests > > Now that we have shell tests, install them. > > Developers don't need this pass, as 'perf test' will look first at the > in tree scripts at tools/perf/tests/shell/. > > Cc: Adrian Hunter > Cc: David Ahern > Cc: Jiri Olsa > Cc: Michael Petlan > Cc: Namhyung Kim > Cc: Thomas Richter > Cc: Wang Nan > Link: http://lkml.kernel.org/n/tip-j21u4v0jsehi0lpwqwjb4j45@git.kernel.org > Signed-off-by: Arnaldo Carvalho de Melo > --- > tools/perf/Makefile.perf | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf > index c1f7884..eb13567 100644 > --- a/tools/perf/Makefile.perf > +++ b/tools/perf/Makefile.perf > @@ -760,7 +760,9 @@ install-tests: all install-gtk > $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests'; \ > $(INSTALL) tests/attr.py '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests'; \ > $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr'; \ > - $(INSTALL) tests/attr/* '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr' > + $(INSTALL) tests/attr/* '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr'; \ > + $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/shell'; \ > + $(INSTALL) tests/shell/*.sh '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/shell' > > install-bin: install-tools install-tests install-traceevent-plugins > >