From: Jiri Olsa <jolsa@redhat.com>
To: Kan Liang <kan.liang@intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org,
ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V6 6/6] perf,tests: Add tests to callgraph and time parse
Date: Wed, 29 Jul 2015 13:53:14 +0200 [thread overview]
Message-ID: <20150729115314.GE9606@krava.brq.redhat.com> (raw)
In-Reply-To: <1437999699-19632-7-git-send-email-kan.liang@intel.com>
On Mon, Jul 27, 2015 at 08:21:39AM -0400, Kan Liang wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> Add tests in tests/parse-events.c to check callgraph and time option
>
> Signed-off-by: Kan Liang <kan.liang@intel.com>
> ---
> tools/perf/tests/parse-events.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
> index f65bb89..fa733d5 100644
> --- a/tools/perf/tests/parse-events.c
> +++ b/tools/perf/tests/parse-events.c
> @@ -479,6 +479,29 @@ static int test__checkevent_pmu_name(struct perf_evlist *evlist)
> return 0;
> }
>
> +static int test__checkevent_pmu_partial_time_callgraph(struct perf_evlist *evlist)
> +{
> + struct perf_evsel *evsel = perf_evlist__first(evlist);
> +
> + /* cpu/config=1,callgraph=fp,time,period=100000/ */
> + TEST_ASSERT_VAL("wrong number of entries", 2 == evlist->nr_entries);
> + TEST_ASSERT_VAL("wrong type", PERF_TYPE_RAW == evsel->attr.type);
> + TEST_ASSERT_VAL("wrong config", 1 == evsel->attr.config);
> + TEST_ASSERT_VAL("wrong period", 100000 == evsel->attr.sample_period);
> + TEST_ASSERT_VAL("wrong callgraph", PERF_SAMPLE_CALLCHAIN & evsel->attr.sample_type);
> + TEST_ASSERT_VAL("wrong time", PERF_SAMPLE_TIME & evsel->attr.sample_type);
> +
> + /* cpu/config=2,callgraph=no,time=0,period=2000/ */
> + evsel = perf_evsel__next(evsel);
> + TEST_ASSERT_VAL("wrong type", PERF_TYPE_RAW == evsel->attr.type);
> + TEST_ASSERT_VAL("wrong config", 2 == evsel->attr.config);
> + TEST_ASSERT_VAL("wrong period", 2000 == evsel->attr.sample_period);
> + TEST_ASSERT_VAL("wrong callgraph", !(PERF_SAMPLE_CALLCHAIN & evsel->attr.sample_type));
> + TEST_ASSERT_VAL("wrong time", !(PERF_SAMPLE_TIME & evsel->attr.sample_type));
hum, this cannot pass right? we dont call perf_evsel__config in this test..
jirka
prev parent reply other threads:[~2015-07-29 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 12:21 [PATCH RFC V6 0/6] per event callgraph and time support Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 1/6] perf tools: Add support for event post configuration Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 2/6] perf tools: Force period term to overload global settings Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 3/6] perf,tools: introduce callgraph_set for callgraph option Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 4/6] perf,tool: per-event time support Kan Liang
2015-07-29 11:02 ` Jiri Olsa
2015-07-27 12:21 ` [PATCH RFC V6 5/6] perf,tool: per-event callgraph support Kan Liang
2015-07-29 11:20 ` Jiri Olsa
2015-07-29 11:48 ` Jiri Olsa
2015-07-29 11:50 ` Jiri Olsa
2015-07-27 12:21 ` [PATCH RFC V6 6/6] perf,tests: Add tests to callgraph and time parse Kan Liang
2015-07-29 11:53 ` Jiri Olsa [this message]
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=20150729115314.GE9606@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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
all inboxes | Powered by JetHome®