linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Ian Rogers <irogers@google.com>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Kajol Jain <kjain@linux.ibm.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Disha Goel <disgoel@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] perf test: Fix parse-events tests to skip parametrized events
Date: Thu, 7 Sep 2023 22:25:00 +0530	[thread overview]
Message-ID: <EF349DBF-8993-425F-BE39-335639AC0BC0@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAP-5=fXJNqokOKJmu1n1kXUqaqabQrsXw42FVi-MrZb3Ss5R-A@mail.gmail.com>



> On 18-Aug-2023, at 12:07 AM, Ian Rogers <irogers@google.com> wrote:
> 
> On Sun, Aug 6, 2023 at 9:50 PM 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".
> 
> I'd say this is different, the "?" is really ugly. On other
> architectures the problem is solved by having >1 PMU, domain and core
> can be meta-data associated with the PMU. If we want to aggregate
> based on domain and core in the perf tool, it will need a different
> way of solving the problem for Power. Skipping the test is just
> pushing this problem down the road.

Hi Ian

Thanks for the comments. We will check on this for powerpc.
> 
>> 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>
>> ---
>> tools/perf/tests/parse-events.c | 32 ++++++++++++++++++++++++++++++++
>> 1 file changed, 32 insertions(+)
>> 
>> diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
>> index b2f82847e4c3..605373c7d005 100644
>> --- a/tools/perf/tests/parse-events.c
>> +++ b/tools/perf/tests/parse-events.c
>> @@ -2504,7 +2504,11 @@ 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 + 256];
> 
> By definition paths can't be longer than PATH_MAX.
Yeah, my bad. Will fix this.

> 
>> +               char *buf = NULL;
>> +               FILE *file;
>>                struct dirent *ent;
>> +               size_t len = 0;
>>                DIR *dir;
>>                int err;
>> 
>> @@ -2528,11 +2532,39 @@ 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;
>> +                       int skip = 0;
> 
> Prefer a boolean. Prefer is_event_parameterized over skip to make
> variable name more intention revealing.
Sure
> 
>> 
>>                        /* Names containing . are special and cannot be used directly */
>>                        if (strchr(ent->d_name, '.'))
>>                                continue;
>> 
>> +                       /* exclude parametrized ones (name contains '?') */
>> +                       snprintf(pmu_event, PATH_MAX + 256, "%s%s", path, ent->d_name);
> 
> Use sizeof(pmu_event) rather than "PATH_MAX + 256".

Will send V2 with these changes
> 
> Thanks,
> Ian
> 
>> +                       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, '?'))
>> +                               skip = 1;
>> +
>> +                       free(buf);
>> +                       buf = NULL;
>> +                       fclose(file);
>> +
>> +                       if (skip == 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 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  4:50 [PATCH] perf test: Fix parse-events tests to skip parametrized events Athira Rajeev
2023-08-07  6:10 ` Sachin Sant
2023-08-17 17:30   ` Athira Rajeev
2023-08-17 18:37 ` Ian Rogers
2023-09-07 16:55   ` Athira Rajeev [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=EF349DBF-8993-425F-BE39-335639AC0BC0@linux.vnet.ibm.com \
    --to=atrajeev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=irogers@google.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).