mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Petlan <mpetlan@redhat.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: tmricht@linux.vnet.ibm.com, namhyung@kernel.org,
	dsahern@gmail.com, Jiri Olsa <jolsa@redhat.com>,
	tglx@linutronix.de, hpa@zytor.com, mingo@kernel.org,
	adrian.hunter@intel.com, wangnan0@huawei.com,
	linux-kernel@vger.kernel.org, acme@kernel.org
Subject: Re: [tip:perf/core] perf test shell: Install shell tests
Date: Mon, 14 Aug 2017 23:01:57 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1708142247130.13365@Diego> (raw)
In-Reply-To: <20170814202854.GC2641@redhat.com>

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]

  reply	other threads:[~2017-08-14 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 17:46 tip-bot for Arnaldo Carvalho de Melo
2017-08-14 18:44 ` Michael Petlan
2017-08-14 20:28   ` Arnaldo Carvalho de Melo
2017-08-14 21:01     ` Michael Petlan [this message]
2017-08-15 15:23       ` Arnaldo Carvalho de Melo
2017-08-15 22:31         ` Michael Petlan

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=alpine.LRH.2.20.1708142247130.13365@Diego \
    --to=mpetlan@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tmricht@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.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

all inboxes | Powered by JetHome®