From: Kim Phillips <kim.phillips@amd.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
Joao Martins <joao.m.martins@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Mark Rutland <mark.rutland@arm.com>,
Michael Petlan <mpetlan@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <robert.richter@amd.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 2/2] perf tools: Improve IBS error handling
Date: Thu, 18 Nov 2021 16:45:28 -0600 [thread overview]
Message-ID: <073f5ae0-0d1d-bbeb-acc6-a10ba2376908@amd.com> (raw)
In-Reply-To: <8a8583dc-5a5d-f107-8ef0-6be96e2f9095@amd.com>
On 10/7/21 2:17 PM, Kim Phillips wrote:
> On 10/7/21 12:28 PM, Jiri Olsa wrote:
>> On Mon, Oct 04, 2021 at 04:41:14PM -0500, Kim Phillips wrote:
>>> ---
>>> tools/perf/util/evsel.c | 24 ++++++++++++++++++++++++
>>> 1 file changed, 24 insertions(+)
>>>
>>> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
>>> index b915840690d4..f8a9cbd99314 100644
>>> --- a/tools/perf/util/evsel.c
>>> +++ b/tools/perf/util/evsel.c
>>> @@ -2743,9 +2743,22 @@ static bool find_process(const char *name)
>>> return ret ? false : true;
>>> }
>>> +static bool is_amd(const char *arch, const char *cpuid)
>>> +{
>>> + return arch && !strcmp("x86", arch) && cpuid && strstarts(cpuid, "AuthenticAMD");
>>> +}
>>> +
>>> +static bool is_amd_ibs(struct evsel *evsel)
>>> +{
>>> + return evsel->core.attr.precise_ip || !strncmp(evsel->pmu_name, "ibs", 3);
>>> +}
>>> +
>>> int evsel__open_strerror(struct evsel *evsel, struct target *target,
>>> int err, char *msg, size_t size)
>>> {
>>> + struct perf_env *env = evsel__env(evsel);
>>> + const char *arch = perf_env__arch(env);
>>> + const char *cpuid = perf_env__cpuid(env);
>>> char sbuf[STRERR_BUFSIZE];
>>> int printed = 0, enforced = 0;
>>> @@ -2841,6 +2854,17 @@ int evsel__open_strerror(struct evsel *evsel, struct target *target,
>>> return scnprintf(msg, size, "wrong clockid (%d).", clockid);
>>> if (perf_missing_features.aux_output)
>>> return scnprintf(msg, size, "The 'aux_output' feature is not supported, update the kernel.");
>>> + if (is_amd(arch, cpuid)) {
>>> + if (is_amd_ibs(evsel)) {
>>
>> would single 'is_amd_ibs' call be better? checking on both amd and ibs
>
> Good suggestion. If you look at the later patch in the
> BRS series, I have rewritten it to add the new
> AMD PMU like so:
>
> if (is_amd()) {
> if (is_amd_ibs()) {
> if (evsel->this)
> return
> if (evsel->that)
> return
> }
> + if (is_amd_brs()) {
> + if (evsel->this)
> + return
> + if (evsel->that)
> + return
> + }
> }
>
> Below is the full proposed replacement patch for patch 12
> of 13 of the BRS series.
>
> Another option is to have the is_amd_{ibs,brs} functions
> call is_amd() themselves, so the if (evsel->) code could be
> unindented by one tab, would that be better?
No reply, so guessing not.
Arnaldo, can these two patches be applied please?
Thanks,
Kim
next prev parent reply other threads:[~2021-11-18 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 21:41 [PATCH 1/2] perf evsel: Make evsel__env always return a valid env Kim Phillips
2021-10-04 21:41 ` [PATCH 2/2] perf tools: Improve IBS error handling Kim Phillips
2021-10-07 17:28 ` Jiri Olsa
2021-10-07 19:17 ` Kim Phillips
2021-11-18 22:45 ` Kim Phillips [this message]
2021-11-23 8:40 ` kajoljain
2021-11-23 15:25 ` Kim Phillips
2021-11-24 8:00 ` kajoljain
2021-11-29 22:09 ` Kim Phillips
2021-12-08 6:33 ` kajoljain
2021-12-08 17:14 ` Kim Phillips
2021-11-23 8:26 ` [PATCH 1/2] perf evsel: Make evsel__env always return a valid env kajoljain
2022-03-22 21:36 ` Arnaldo Carvalho de Melo
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=073f5ae0-0d1d-bbeb-acc6-a10ba2376908@amd.com \
--to=kim.phillips@amd.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=joao.m.martins@oracle.com \
--cc=jolsa@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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®