linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ian Rogers <irogers@google.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: maddy@linux.ibm.com, kjain@linux.ibm.com,
	adrian.hunter@intel.com, acme@kernel.org,
	linux-perf-users@vger.kernel.org, jolsa@kernel.org,
	namhyung@kernel.org, disgoel@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2] perf test: Fix parse-events tests to skip parametrized events
Date: Thu, 7 Sep 2023 15:39:15 -0700	[thread overview]
Message-ID: <CAP-5=fWTSSH2vgxK7LM23mK-PbsOoZc+ZNq_8dL1X=dYMKemfA@mail.gmail.com> (raw)
In-Reply-To: <20230907165933.36442-1-atrajeev@linux.vnet.ibm.com>

On Thu, Sep 7, 2023 at 9:59 AM Athira Rajeev
<atrajeev@linux.vnet.ibm.com> wrote:
>
> Testcase "Parsing of all PMU events from sysfs" parse events for
> all PMUs, and not just cpu. In case of powerpc, the PowerVM
> environment supports events from hv_24x7 and hv_gpci PMU which
> is of example format like below:
>
> - hv_24x7/CPM_ADJUNCT_INST,domain=?,core=?/
> - hv_gpci/event,partition_id=?/
>
> The value for "?" needs to be filled in depending on system
> configuration. It is better to skip these parametrized events
> in this test as it is done in:
> 'commit b50d691e50e6 ("perf test: Fix "all PMU test" to skip
> parametrized events")' which handled a simialr instance with
> "all PMU test".
>
> Fix parse-events test to skip parametrized events since
> it needs proper setup of the parameters.
>
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>

Tested-by: Ian Rogers <irogers@google.com>

Thanks,
Ian

> ---
> Changelog:
> v1 -> v2:
>  Addressed review comments from Ian. Updated size of
>  pmu event name variable and changed bool name which is
>  used to skip the test.
>
>  tools/perf/tests/parse-events.c | 38 +++++++++++++++++++++++++++++++++
>  1 file changed, 38 insertions(+)
>
> diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
> index 658fb9599d95..1ecaeceb69f8 100644
> --- a/tools/perf/tests/parse-events.c
> +++ b/tools/perf/tests/parse-events.c
> @@ -2514,9 +2514,14 @@ static int test__pmu_events(struct test_suite *test __maybe_unused, int subtest
>         while ((pmu = perf_pmus__scan(pmu)) != NULL) {
>                 struct stat st;
>                 char path[PATH_MAX];
> +               char pmu_event[PATH_MAX];
> +               char *buf = NULL;
> +               FILE *file;
>                 struct dirent *ent;
> +               size_t len = 0;
>                 DIR *dir;
>                 int err;
> +               int n;
>
>                 snprintf(path, PATH_MAX, "%s/bus/event_source/devices/%s/events/",
>                         sysfs__mountpoint(), pmu->name);
> @@ -2538,11 +2543,44 @@ static int test__pmu_events(struct test_suite *test __maybe_unused, int subtest
>                         struct evlist_test e = { .name = NULL, };
>                         char name[2 * NAME_MAX + 1 + 12 + 3];
>                         int test_ret;
> +                       bool is_event_parameterized = 0;
>
>                         /* Names containing . are special and cannot be used directly */
>                         if (strchr(ent->d_name, '.'))
>                                 continue;
>
> +                       /* exclude parametrized ones (name contains '?') */
> +                       n = snprintf(pmu_event, sizeof(pmu_event), "%s%s", path, ent->d_name);
> +                       if (n >= PATH_MAX) {
> +                               pr_err("pmu event name crossed PATH_MAX(%d) size\n", PATH_MAX);
> +                               continue;
> +                       }
> +
> +                       file = fopen(pmu_event, "r");
> +                       if (!file) {
> +                               pr_debug("can't open pmu event file for '%s'\n", ent->d_name);
> +                               ret = combine_test_results(ret, TEST_FAIL);
> +                               continue;
> +                       }
> +
> +                       if (getline(&buf, &len, file) < 0) {
> +                               pr_debug(" pmu event: %s is a null event\n", ent->d_name);
> +                               ret = combine_test_results(ret, TEST_FAIL);
> +                               continue;
> +                       }
> +
> +                       if (strchr(buf, '?'))
> +                               is_event_parameterized = 1;
> +
> +                       free(buf);
> +                       buf = NULL;
> +                       fclose(file);
> +
> +                       if (is_event_parameterized == 1) {
> +                               pr_debug("skipping parametrized PMU event: %s which contains ?\n", pmu_event);
> +                               continue;
> +                       }
> +
>                         snprintf(name, sizeof(name), "%s/event=%s/u", pmu->name, ent->d_name);
>
>                         e.name  = name;
> --
> 2.31.1
>

  reply	other threads:[~2023-09-07 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 16:59 [PATCH V2] perf test: Fix parse-events tests to skip parametrized events Athira Rajeev
2023-09-07 22:39 ` Ian Rogers [this message]
2023-09-08  5:34 ` Sachin Sant
2023-09-08 14:18   ` Athira Rajeev
2023-09-13  5:01     ` Athira Rajeev
2023-09-25 17:37       ` Arnaldo Carvalho de Melo
2023-09-26 22:37         ` Namhyung Kim
2023-09-27  4:29           ` Athira Rajeev
2023-09-25  8:03 ` kajoljain

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='CAP-5=fWTSSH2vgxK7LM23mK-PbsOoZc+ZNq_8dL1X=dYMKemfA@mail.gmail.com' \
    --to=irogers@google.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=jolsa@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).