From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Leo Yan <leo.yan@arm.com>
Cc: 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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] perf probe: Improve log for long event name failure
Date: Mon, 14 Oct 2024 11:24:43 +0900 [thread overview]
Message-ID: <20241014112443.97b129e774d9f313dc32568e@kernel.org> (raw)
In-Reply-To: <20241012204725.928794-4-leo.yan@arm.com>
On Sat, 12 Oct 2024 21:47:25 +0100
Leo Yan <leo.yan@arm.com> wrote:
> If a symbol name is longer than the maximum event length (64 bytes), the
> perf tool reports error:
>
> # perf probe -x test_cpp_mangle --add "this_is_a_very_very_long_print_data_abcdefghijklmnopqrstuvwxyz(int)"
> snprintf() failed: -7; the event name nbase='this_is_a_very_very_long_print_data_abcdefghijklmnopqrstuvwxyz(int)' is too long
> Error: Failed to add events.
>
> An information is missed in the log that the symbol name and the event
> name can be set separately. Especially, this is recommended for adding
> probe for a long symbol.
>
> This commit refines the log for reminding event syntax.
>
> After:
>
> # perf probe -x test_cpp_mangle --add "this_is_a_very_very_long_print_data_abcdefghijklmnopqrstuvwxyz(int)"
> snprintf() failed: -7; the event name 'this_is_a_very_very_long_print_data_abcdefghijklmnopqrstuvwxyz(int)' is too long
> Hint: Set a shorter event with syntax "EVENT=PROBEDEF"
> EVENT: Event name (max length: 64 bytes).
> Error: Failed to add events.
>
Nice!
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you,
> Signed-off-by: Leo Yan <leo.yan@arm.com>
> ---
> tools/perf/util/probe-event.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 224ec6818803..2a2fc5e78c5c 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -2760,7 +2760,10 @@ static int get_new_event_name(char *buf, size_t len, const char *base,
> /* Try no suffix number */
> ret = e_snprintf(buf, len, "%s%s", nbase, ret_event ? "__return" : "");
> if (ret < 0) {
> - pr_warning("snprintf() failed: %d; the event name nbase='%s' is too long\n", ret, nbase);
> + pr_warning("snprintf() failed: %d; the event name '%s' is too long\n"
> + " Hint: Set a shorter event with syntax \"EVENT=PROBEDEF\"\n"
> + " EVENT: Event name (max length: %d bytes).\n",
> + ret, nbase, MAX_EVENT_NAME_LEN);
> goto out;
> }
> if (!strlist__has_entry(namelist, buf))
> @@ -2780,7 +2783,10 @@ static int get_new_event_name(char *buf, size_t len, const char *base,
> for (i = 1; i < MAX_EVENT_INDEX; i++) {
> ret = e_snprintf(buf, len, "%s_%d", nbase, i);
> if (ret < 0) {
> - pr_debug("snprintf() failed: %d\n", ret);
> + pr_warning("Add suffix failed: %d; the event name '%s' is too long\n"
> + " Hint: Set a shorter event with syntax \"EVENT=PROBEDEF\"\n"
> + " EVENT: Event name (max length: %d bytes).\n",
> + ret, nbase, MAX_EVENT_NAME_LEN);
> goto out;
> }
> if (!strlist__has_entry(namelist, buf))
> --
> 2.25.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2024-10-14 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 20:47 [PATCH v3 0/3] perf probe: Improve logs for long name string Leo Yan
2024-10-12 20:47 ` [PATCH v3 1/3] perf probe: Use the MAX_EVENT_NAME_LEN macro Leo Yan
2024-10-14 0:46 ` Masami Hiramatsu
2024-10-12 20:47 ` [PATCH v3 2/3] perf probe: Check group string length Leo Yan
2024-10-12 20:47 ` [PATCH v3 3/3] perf probe: Improve log for long event name failure Leo Yan
2024-10-14 2:24 ` Masami Hiramatsu [this message]
2024-10-17 16:39 ` [PATCH v3 0/3] perf probe: Improve logs for long name string 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=20241014112443.97b129e774d9f313dc32568e@kernel.org \
--to=mhiramat@kernel.org \
--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=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®