From: Namhyung Kim <namhyung@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 3/3] perf tools: add 'keep tracking' test
Date: Tue, 13 Aug 2013 11:33:56 +0900 [thread overview]
Message-ID: <87iozawc8b.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1375882231-18339-4-git-send-email-adrian.hunter@intel.com> (Adrian Hunter's message of "Wed, 7 Aug 2013 16:30:31 +0300")
On Wed, 7 Aug 2013 16:30:31 +0300, Adrian Hunter wrote:
> Add a test for the newly added PERF_COUNT_SW_DUMMY event.
> The test checks that tracking events continue when an
> event is disabled but a dummy software event is not
> disabled.
[SNIP]
> +int test__keep_tracking(void)
> +{
> + struct perf_record_opts opts = {
> + .mmap_pages = UINT_MAX,
> + .user_freq = UINT_MAX,
> + .user_interval = ULLONG_MAX,
> + .freq = 4000,
> + .target = {
> + .uses_mmap = true,
> + },
> + };
> + struct thread_map *threads = NULL;
> + struct cpu_map *cpus = NULL;
> + struct perf_evlist *evlist = NULL;
> + struct perf_evsel *evsel = NULL;
> + int found, err = -1;
> + const char *comm;
> +
> + threads = thread_map__new(-1, getpid(), UINT_MAX);
> + CHECK_NOT_NULL__(threads);
> +
> + cpus = cpu_map__new(NULL);
> + CHECK_NOT_NULL__(cpus);
> +
> + evlist = perf_evlist__new();
> + CHECK_NOT_NULL__(evlist);
> +
> + perf_evlist__set_maps(evlist, cpus, threads);
> +
> + CHECK__(parse_events(evlist, "dummy:u"));
> + CHECK__(parse_events(evlist, "cycles:u"));
> +
> + perf_evlist__config(evlist, &opts);
> +
> + evsel = perf_evlist__first(evlist);
> +
> + evsel->attr.comm = 1;
> + evsel->attr.disabled = 1;
> + evsel->attr.enable_on_exec = 0;
> +
> + CHECK__(perf_evlist__open(evlist));
> +
> + CHECK__(perf_evlist__mmap(evlist, UINT_MAX, false));
> +
> + /*
> + * First, test that a 'comm' event can be found when the event is
> + * enabled.
> + */
> +
> + perf_evlist__enable(evlist);
> +
> + comm = "Test COMM 1";
> + CHECK__(prctl(PR_SET_NAME, (unsigned long)comm, 0, 0, 0));
> +
> + perf_evlist__disable(evlist);
> +
> + found = find_comm(evlist, comm);
> + if (found != 1) {
> + pr_debug("First time, failed to find tracking event.\n");
> + goto out_err;
> + }
> +
> + /*
> + * Secondly, test that a 'comm' event can be found when the event is
> + * disabled with the dummy event still enabled.
> + */
> +
> + perf_evlist__enable(evlist);
> +
> + evsel = perf_evlist__last(evlist);
> +
> + CHECK__(perf_evlist__disable_event(evlist, evsel));
> +
> + comm = "Test COMM 2";
> + CHECK__(prctl(PR_SET_NAME, (unsigned long)comm, 0, 0, 0));
> +
> + perf_evlist__disable(evlist);
> +
> + found = find_comm(evlist, comm);
> + if (found != 1) {
> + pr_debug("Seconf time, failed to find tracking event.\n");
> + goto out_err;
> + }
> +
> + err = 0;
> +
> +out_err:
> + if (evlist) {
> + perf_evlist__disable(evlist);
It seems the both of goto out_err already called perf_evlist__disable().
Thanks,
Namhyung
> + perf_evlist__munmap(evlist);
> + perf_evlist__close(evlist);
> + perf_evlist__delete(evlist);
> + }
> + if (cpus)
> + cpu_map__delete(cpus);
> + if (threads)
> + thread_map__delete(threads);
> +
> + return err;
> +}
next prev parent reply other threads:[~2013-08-13 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 13:30 [PATCH 0/3] perf: add a dummy software event to keep tracking Adrian Hunter
2013-08-07 13:30 ` [PATCH 1/3] " Adrian Hunter
2013-08-26 13:15 ` Adrian Hunter
2013-08-26 13:53 ` Arnaldo Carvalho de Melo
2013-08-26 16:16 ` Peter Zijlstra
2013-08-07 13:30 ` [PATCH 2/3] perf tools: add support for PERF_COUNT_SW_DUMMY Adrian Hunter
2013-08-07 13:30 ` [PATCH 3/3] perf tools: add 'keep tracking' test Adrian Hunter
2013-08-13 2:33 ` Namhyung Kim [this message]
2013-08-26 13:13 ` Adrian Hunter
2013-08-13 2:28 ` [PATCH 0/3] perf: add a dummy software event to keep tracking Namhyung Kim
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=87iozawc8b.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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