From: James Clark <james.clark@arm.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tchen168@asu.edu, Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH v2 2/3] perf parse-events: Improve error location of terms cloned from an event
Date: Thu, 1 Feb 2024 13:54:34 +0000 [thread overview]
Message-ID: <f98d310e-5e25-2e71-0159-7b598d15f1ee@arm.com> (raw)
In-Reply-To: <20240131134940.593788-2-irogers@google.com>
On 31/01/2024 13:49, Ian Rogers wrote:
> A PMU event/alias will have a set of format terms that replace it when
> an event is parsed. The location of the terms is their position when
> parsed for the event/alias either from sysfs or json. This location is
> of little use when an event fails to parse as the error will be given
> in terms of the location in the string of events parsed not the json
> or sysfs string. Fix this by making the cloned terms location that of
> the event/alias.
>
> If a cloned term from an event/alias is invalid the bad format is hard
> to determine from the error string. Add the name of the bad format
> into the error string.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
Reviewed-by: James Clark <james.clark@arm.com>
> ---
> These fixes were inspired by the poor error output in:
> https://lore.kernel.org/linux-perf-users/alpine.LRH.2.20.2401300733310.11354@Diego/
> ---
> tools/perf/util/pmu.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 355f813f960d..437386dedd5c 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -657,7 +657,7 @@ static int pmu_aliases_parse(struct perf_pmu *pmu)
> return 0;
> }
>
> -static int pmu_alias_terms(struct perf_pmu_alias *alias, struct list_head *terms)
> +static int pmu_alias_terms(struct perf_pmu_alias *alias, int err_loc, struct list_head *terms)
> {
> struct parse_events_term *term, *cloned;
> struct parse_events_terms clone_terms;
> @@ -675,6 +675,7 @@ static int pmu_alias_terms(struct perf_pmu_alias *alias, struct list_head *terms
> * which we don't want for implicit terms in aliases.
> */
> cloned->weak = true;
> + cloned->err_term = cloned->err_val = err_loc;
> list_add_tail(&cloned->list, &clone_terms.terms);
> }
> list_splice_init(&clone_terms.terms, terms);
> @@ -1363,8 +1364,8 @@ static int pmu_config_term(const struct perf_pmu *pmu,
>
> parse_events_error__handle(err, term->err_val,
> asprintf(&err_str,
> - "value too big for format, maximum is %llu",
> - (unsigned long long)max_val) < 0
> + "value too big for format (%s), maximum is %llu",
> + format->name, (unsigned long long)max_val) < 0
> ? strdup("value too big for format")
> : err_str,
> NULL);
> @@ -1518,7 +1519,7 @@ int perf_pmu__check_alias(struct perf_pmu *pmu, struct parse_events_terms *head_
> alias = pmu_find_alias(pmu, term);
> if (!alias)
> continue;
> - ret = pmu_alias_terms(alias, &term->list);
> + ret = pmu_alias_terms(alias, term->err_term, &term->list);
> if (ret) {
> parse_events_error__handle(err, term->err_term,
> strdup("Failure to duplicate terms"),
next prev parent reply other threads:[~2024-02-01 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:49 [PATCH v2 1/3] perf tsc: Add missing newlines to debug statements Ian Rogers
2024-01-31 13:49 ` [PATCH v2 2/3] perf parse-events: Improve error location of terms cloned from an event Ian Rogers
2024-02-01 13:54 ` James Clark [this message]
2024-01-31 13:49 ` [PATCH v2 3/3] perf parse-events: Print all errors Ian Rogers
2024-02-01 13:59 ` James Clark
2024-01-31 13:51 ` [PATCH v2 1/3] perf tsc: Add missing newlines to debug statements Ian Rogers
2024-02-06 0:18 ` Namhyung Kim
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=f98d310e-5e25-2e71-0159-7b598d15f1ee@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.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=tchen168@asu.edu \
/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®