linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: acme@kernel.org, irogers@google.com, 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
Subject: Re: [PATCH v2 2/2] perf test: Add event group test
Date: Thu, 1 Dec 2022 09:02:08 -0500	[thread overview]
Message-ID: <7449d858-2110-1ddf-f7e1-013015cbd791@linux.intel.com> (raw)
In-Reply-To: <62399b9c-d5ef-4c56-4592-d2cf1af503d6@amd.com>



On 2022-12-01 4:13 a.m., Ravi Bangoria wrote:
> Hi Kan,
> 
> Thanks for the review.
> 
>>> +static int setup_uncore_event(void)
>>> +{
>>> +	struct perf_pmu *pmu;
>>> +
>>> +	if (list_empty(&pmus))
>>> +		perf_pmu__scan(NULL);
>>> +
>>> +	perf_pmus__for_each_pmu(pmu) {
>>> +		if (pmu->is_uncore) {
>>
>> Always using the first uncore PMU may trigger false alarm on some Intel
>> platforms. For example, Intel has free running uncore PMUs (e.g.,
>> uncore_imc_free_running_0), which only supports special event encoding
>> 0xff. The config 0 must fails.
>> You may want to add the below check to ignore the free running uncore PMUs.
>>                         if (strstr(pmu->name, "free_running"))
>>                                 continue;
>>
>>
>> Also, some uncore PMUs only support two counters. But the test assumes
>> that the number of counters > 2. You may want to limit the size of the
>> group for 2 for a pure uncore group.
> 
> That seems hacky. Instead of ignoring, would it be possible to provide
> a list of testable pmus? Example with random values:
> 
>   /* 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 }

>       { "intel_xxx_pmu2", 0xff },   /* Intel */

Intel doesn't have such uncore PMUs.

>       { "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.

Maybe we should fall back to the first uncore PMU and try again if
nothing match the uncore_pmus[].

Thanks,
Kan
> 
> Ofcourse, this should work for all architectures. Arm, PowerPC, s390 folks?
> 
> Thanks,
> Ravi

  reply	other threads:[~2022-12-01 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 11:19 [PATCH v2 0/2] perf test: Add event group test 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 [this message]
2022-12-01 15:29         ` Ravi Bangoria
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=7449d858-2110-1ddf-f7e1-013015cbd791@linux.intel.com \
    --to=kan.liang@linux.intel.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=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=ravi.bangoria@amd.com \
    --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;
as well as URLs for NNTP newsgroup(s).