Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1711463
| From | Michael Petlan <mpetlan@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [tip:perf/core] perf test shell: Install shell tests |
| Date | 2017-08-14 23:10 +0200 |
| Message-ID | <ueuMy-IV-31@gated-at.bofh.it> (permalink) |
| References | <uerF1-76t-29@gated-at.bofh.it> <uesB5-7Hs-33@gated-at.bofh.it> <ueu9P-gF-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 14 Aug 2017, Arnaldo Carvalho de Melo wrote: > Em Mon, Aug 14, 2017 at 08:44:14PM +0200, Michael Petlan escreveu: > > Hi Arnaldo! > > > > Maybe this would be the right time to incorporate the shell-based > > perftool-testsuite [1] into perf-test, wouldn't it? > > Perhaps its time, yes. Some questions: > > Do these tests assume that perf was built in some particular way, i.e. > as it is packaged for RHEL? Of course I run the testsuite most often on RHEL, but it should be distro-agnostic, worked on Debian with their perf as well as with vanilla kernel/perf build from Linus' repo... It somehow assumes having kernel-debuginfo available (but this does not necessarily mean kernel-debuginfo RHEL package). It runs against 'perf' from path or against $CMD_PERF if this variable is defined. > > One thing that came to mind from a report from Kim Phillips, that I > addressed (to some extent) after this sending this first patchkit to > Ingo was that perf can be built in many ways, for instance, without > 'perf probe', or with 'perf probe' but without DWARF support, which will > allow some features to be tested while others should cause the test > needing not-builtin features to just return '2', that will make it be > marked as "Skip" in the output. > It has mechanisms for skipping things if they aren't supported, but definitely not *all*. E.g. it detects uprobe/kprobe support, POWER8 hv_24x7 events support, Intel uncore support, HW breakpoint events availablitity, etc. But as I said, perf without perf-probe subcommand would probably fail, because I wasn't aware of such possibility... Anyway, it is easily fixable... The suite has a mechanism for skipping particular tests. If there is a way to detect a feature support, it is easy to use it as a condition. The dwarf support might be more difficult, because afaik, there's no way to find out whether dwarf support just does not work or is disabled on purpose... Michael > - Arnaldo > > > 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: > > [SNIP]
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[tip:perf/core] perf test shell: Install shell tests tip-bot for Arnaldo Carvalho de Melo <tipbot@zytor.com> - 2017-08-14 19:50 +0200
Re: [tip:perf/core] perf test shell: Install shell tests Michael Petlan <mpetlan@redhat.com> - 2017-08-14 20:50 +0200
Re: [tip:perf/core] perf test shell: Install shell tests Arnaldo Carvalho de Melo <acme@redhat.com> - 2017-08-14 22:30 +0200
Re: [tip:perf/core] perf test shell: Install shell tests Michael Petlan <mpetlan@redhat.com> - 2017-08-14 23:10 +0200
Re: [tip:perf/core] perf test shell: Install shell tests Arnaldo Carvalho de Melo <acme@kernel.org> - 2017-08-15 17:30 +0200
Re: [tip:perf/core] perf test shell: Install shell tests Michael Petlan <mpetlan@redhat.com> - 2017-08-16 00:40 +0200
csiph-web