From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@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>,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>,
James Clark <james.clark@linaro.org>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linux.dev>,
Yicong Yang <yangyicong@hisilicon.com>,
Weilin Wang <weilin.wang@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/8] perf stat: Display "none" for NaN with metric only json
Date: Tue, 8 Oct 2024 15:38:39 -0700 [thread overview]
Message-ID: <ZwW0b8km5DnaOETr@google.com> (raw)
In-Reply-To: <20241004234120.1495209-4-irogers@google.com>
On Fri, Oct 04, 2024 at 04:41:15PM -0700, Ian Rogers wrote:
> Return earlier for an empty unit case. If snprintf of the fmt doesn't
> produce digits between vals and ends, as happens with NaN, make the
> value "none" as happens in print_metric_end.
Then it could be "NaN" or is there any other case? But probably "none"
would be more generic.
Thanks,
Namhyung
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/util/stat-display.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c
> index 5402998881c4..e392ee5efb45 100644
> --- a/tools/perf/util/stat-display.c
> +++ b/tools/perf/util/stat-display.c
> @@ -609,19 +609,22 @@ static void print_metric_only_json(struct perf_stat_config *config __maybe_unuse
> {
> struct outstate *os = ctx;
> FILE *out = os->fh;
> - char buf[64], *vals, *ends;
> + char buf[64], *ends;
> char tbuf[1024];
> + const char *vals;
>
> if (!valid_only_metric(unit))
> return;
> unit = fixunit(tbuf, os->evsel, unit);
> + if (!unit[0])
> + return;
> snprintf(buf, sizeof(buf), fmt ?: "", val);
> - ends = vals = skip_spaces(buf);
> + vals = ends = skip_spaces(buf);
> while (isdigit(*ends) || *ends == '.')
> ends++;
> *ends = 0;
> - if (!unit[0] || !vals[0])
> - return;
> + if (!vals[0])
> + vals = "none";
> fprintf(out, "%s\"%s\" : \"%s\"", os->first ? "" : ", ", unit, vals);
> os->first = false;
> }
> --
> 2.47.0.rc0.187.ge670bccf7e-goog
>
next prev parent reply other threads:[~2024-10-08 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 23:41 [PATCH v1 0/8] CSV/JSON metric thresholds, fix printf modifiers Ian Rogers
2024-10-04 23:41 ` [PATCH v1 1/8] perf color: Add printf format checking and resolve issues Ian Rogers
2024-10-04 23:41 ` [PATCH v1 2/8] perf stat: Fix/add parameter names for print_metric Ian Rogers
2024-10-04 23:41 ` [PATCH v1 3/8] perf stat: Display "none" for NaN with metric only json Ian Rogers
2024-10-08 22:38 ` Namhyung Kim [this message]
2024-10-08 23:38 ` Ian Rogers
2024-10-04 23:41 ` [PATCH v1 4/8] perf stat: Drop metric-unit if unit is NULL Ian Rogers
2024-10-08 23:27 ` Tim Chen
2024-10-08 23:33 ` Ian Rogers
2024-10-04 23:41 ` [PATCH v1 5/8] perf stat: Change color to threshold in print_metric Ian Rogers
2024-10-04 23:41 ` [PATCH v1 6/8] perf stat: Display metric threshold value in CSV output Ian Rogers
2024-10-04 23:41 ` [PATCH v1 7/8] perf stat: Add metric-threshold to json output Ian Rogers
2024-10-04 23:41 ` [PATCH v1 8/8] perf stat: Disable metric thresholds for CSV/JSON metric-only mode Ian Rogers
2024-10-08 22:47 ` [PATCH v1 0/8] CSV/JSON metric thresholds, fix printf modifiers Namhyung Kim
2024-10-08 23:40 ` Ian Rogers
2024-10-10 0:59 ` 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=ZwW0b8km5DnaOETr@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sumanthk@linux.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=tmricht@linux.ibm.com \
--cc=weilin.wang@intel.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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