From: Ravi Bangoria <ravi.bangoria@amd.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>, irogers@google.com
Cc: acme@kernel.org, jolsa@redhat.com, namhyung@kernel.org,
peterz@infradead.org, mark.rutland@arm.com,
adrian.hunter@intel.com, alexander.shishkin@linux.intel.com,
carsten.haitzler@arm.com, leo.yan@linaro.org,
maddy@linux.ibm.com, kjain@linux.ibm.com,
atrajeev@linux.vnet.ibm.com, tmricht@linux.ibm.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
sandipan.das@amd.com, ananth.narayan@amd.com,
santosh.shukla@amd.com, Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH v2 2/2] perf test: Add event group test
Date: Thu, 1 Dec 2022 20:59:03 +0530 [thread overview]
Message-ID: <0eb0cc59-d28d-8e42-3233-2587123e291d@amd.com> (raw)
In-Reply-To: <7449d858-2110-1ddf-f7e1-013015cbd791@linux.intel.com>
>> /* Uncore pmus that support more than 3 counters */
>> static struct uncore_pmus {
>> char *name;
>> unsigned long config;
>> } uncore_pmus[] = {
>> { "amd_l3", 0x0 },
>> { "amd_df", 0x0 },
>> { "uncore_imc_xxx", 0xff }, /* Intel */
>
> IMC seems a safe choice. AFAIK, we should have at least uncore_imc_0 for
> all the existing Intel platforms. { "uncore_imc_0", 0x1 }
Ok. Ian said he don't see uncore_imc_0 on his tigerlake machine. Are you
sure uncore_imc_0 should be present on all existing Intel platforms?
>> { "intel_xxx_pmu2", 0xff }, /* Intel */
>
> Intel doesn't have such uncore PMUs.
Yeah this was just for example purpose.
>> { "abc_pmu1", 0x0 }, /* Arm */
>> { "hv_24x7", 0xa }, /* PowerPC */
>> { ... },
>> };
>>
>> perf_pmus__for_each_pmu(pmu) {
>> if (pmu present in uncore_pmus[])
>> type[2] = pmu->type;
>> config[2] = pmu->config;> }
>
>
> Not sure the uncore_pmus[] can cover all possible names for all
> architectures.
It doesn't need to cover _all_ possible names. It just needs to cover
minimal set of names which can cover all platforms for that architecture.
> Maybe we should fall back to the first uncore PMU and try again if
> nothing match the uncore_pmus[].
That's a good point. However, this can endup with the same problem you
mentioned: it may trigger false alarm on some platform. So better to
skip the test(and let someone add proper pmu in this list) rather than
proving false negative result?
Thanks,
Ravi
next prev parent reply other threads:[~2022-12-01 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 11:19 [PATCH v2 0/2] " Ravi Bangoria
2022-11-29 11:19 ` [PATCH v2 1/2] perf tool: Move pmus list variable to new a file Ravi Bangoria
2022-11-29 11:19 ` [PATCH v2 2/2] perf test: Add event group test Ravi Bangoria
2022-11-29 20:13 ` Liang, Kan
2022-12-01 9:13 ` Ravi Bangoria
2022-12-01 14:02 ` Liang, Kan
2022-12-01 15:29 ` Ravi Bangoria [this message]
2022-12-01 15:47 ` Liang, Kan
2022-12-01 16:29 ` Ravi Bangoria
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=0eb0cc59-d28d-8e42-3233-2587123e291d@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=carsten.haitzler@arm.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tmricht@linux.ibm.com \
/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®