From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>, Vince Weaver <vince@deater.net>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
Kanaka Juvva <kanaka.d.juvva@intel.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: Perf tests for hw events
Date: Thu, 22 Jan 2015 09:59:52 -0300 [thread overview]
Message-ID: <20150122125952.GA3073@kernel.org> (raw)
In-Reply-To: <20150122124014.GF12079@codeblueprint.co.uk>
Em Thu, Jan 22, 2015 at 12:40:14PM +0000, Matt Fleming escreveu:
> Folks,
>
> In the process of writing perf support for Intel's Cache QoS Monitoring
> feature [0] I've had to write my own userland tests to drive tools/perf
> and indirectly the kernel internals. I'm now getting requests for these
> tests from various people and it occurs to me that they should probably
> live in the kernel tree.
>
> The tests I've got do a couple of things like setting up a perf_event
> cgroup and assigning enough tasks to trigger the RMID recycling code in
> the CQM driver, ensuring that we can run multiple events simultaneously
> (that the event scheduling/rotation code works), etc.
>
> Does anything like this already exist for hw events? I couldn't find
> anything specific to hw events from snooping around in tools/perf/tests.
>
> I propose we add some hw event tests to the kernel tree. These will
> provide,
>
> - regression tests
> - a source of documentation for how to use the events
That is the description for tools/perf/tests/ please send your patches
for adding new entries there.
> We should only test those hw events that are present on a user's
> machine; there's no sense in emulating things.
At some point 'perf test' should grow infrastructure to specify what is
required for a test so that it auto-skips those, possibly not even
bothering the user telling something can't be tested. Right now for
things like tests that requires finding a vmlinux, if it doesn't find
it, it will just print "Skipped", etc.
> Thoughts?
>
> [0] - https://lkml.kernel.org/r/1415999712-5850-1-git-send-email-matt@console-pimps.org
- Arnaldo
next prev parent reply other threads:[~2015-01-22 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 12:40 Perf tests for hw events Matt Fleming
2015-01-22 12:56 ` Jiri Olsa
2015-01-22 17:08 ` Matt Fleming
2015-01-22 12:59 ` Arnaldo Carvalho de Melo [this message]
2015-01-22 17:11 ` Matt Fleming
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=20150122125952.GA3073@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=kanaka.d.juvva@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=vikas.shivappa@linux.intel.com \
--cc=vince@deater.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.