From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: nelakurthi koteswararao <koteswararao18@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: How to check perf commands are producing proper output or not?
Date: Fri, 28 Jan 2011 11:48:11 -0200 [thread overview]
Message-ID: <20110128134811.GB6345@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTikZc4L=-xzmOvqLC00qNHLuqCBOdcD3hofBNfFN@mail.gmail.com>
Em Fri, Jan 28, 2011 at 05:49:00PM +0530, nelakurthi koteswararao escreveu:
> I run the Perftest commands on 2.6.35 tree .
> I want to test perf commands itself whether
> they are producing the correct results or not.
>
> That means..suppose if i have following perf commands
>
> How to write test to test the above commands whether they are producing
> the proper results specific to perf commands or not?
>
> Some tests like checking the processor registers at regular intervals to
> validate
> the perf results ? Any inputs regarding this query...?
That is a good question, we need more tests in tools/perf/builtin-test.c
that do this kinds of validations.
So far I wrote some that generate tracepoint events, but I can envision
for instance, figuring out the size of the L2 processor cache, creating
an array that is of that size, then go on touching it till it trashes
the cache while measuring the relevant event.
- Arnaldo
next parent reply other threads:[~2011-01-28 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikZc4L=-xzmOvqLC00qNHLuqCBOdcD3hofBNfFN@mail.gmail.com>
2011-01-28 13:48 ` Arnaldo Carvalho de Melo [this message]
2011-01-28 14:37 ` How to check perf commands are producing proper output or not? Vince Weaver
2011-01-28 15:43 ` Arnaldo Carvalho de Melo
2011-01-28 22:03 ` Vince Weaver
2011-01-29 13:07 ` Arnaldo Carvalho de Melo
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=20110128134811.GB6345@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=koteswararao18@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).