[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160105232723.GA6620@kernel.org>
Date: Tue, 5 Jan 2016 20:27:23 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Jiri Olsa <jolsa@...hat.com>, jolsa@...nel.org, mingo@...nel.org,
linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] perf, tools, stat: Force C numeric locale for CSV mode
Em Tue, Jan 05, 2016 at 10:28:39PM +0100, Andi Kleen escreveu:
> On Tue, Jan 05, 2016 at 06:17:57PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jan 05, 2016 at 10:05:01PM +0100, Jiri Olsa escreveu:
> > > On Tue, Jan 05, 2016 at 11:17:45AM -0800, Andi Kleen wrote:
> > > > From: Andi Kleen <ak@...ux.intel.com>
> > > >
> > > > Some locales print floating point numbers with a comma instead of a dot.
> > > > This causes problems with CSV mode because it causes extra false CSV
> > > > fields. Force the numeric locale to be always C in CSV mode.
> > > >
> > > > Before:
> > > >
> > > > $ LC_ALL=pl_PL.utf8 perf stat -x, true
> > > > 0,399472,,task-clock,399472,100,00 <---- extra bogus field
> > > > ...
> > > >
> > > > After:
> > > > $ LC_ALL=pl_PL.utf8 ./obj-perf/perf stat -x, true
> > > > 0.338422,,task-clock,338422,100.00
> > > >
> > > > Originally reported in https://github.com/andikleen/pmu-tools/issues/43
> > > >
> > > > Signed-off-by: Andi Kleen <ak@...ux.intel.com>
> > >
> > > Acked-by: Jiri Olsa <jolsa@...nel.org>
> >
> > I wonder what is that other tools do when stumbling on this, i.e.
> > some other tool output that produces values that have the CSV character
> > in it...
>
> Proper CSV supports escaping the separator by putting the whole field
> into quotes. Unfortunately perf stat doesn't output proper CSV,
> the event fields with commas are not quoted.
Right, there is even an RFC for CSV, and for a decade already :-)
https://tools.ietf.org/html/rfc4180
> I usually work around it by using -x\; instead
>
> But the , problem should be still fixed.
Humm, what is the problem then of doing, for example in my case, with a
LC_ALL=pt_BR, that uses commans as the decimal separator:
LC_ALL=C ./obj-perf/perf stat -x, true
I.e. disabling it using the existing shell mecanism?
[root@zoo ~]# export LC_ALL=pt_BR
[root@zoo ~]# perf stat -e cycles -x, usleep 1
1068190,,cycles,1007049,100,00
Bad, but its a side effect of needing to use a locale that uses the CSV
separator in the decimal separator, disabling it for commands where I
want that CSV separator does the trick:
[root@zoo ~]# LC_ALL= perf stat -e cycles -x, usleep 1
895081,,cycles,840687,100.00
[root@zoo ~]#
It is an inconvenience, yeah, having to prefix that for tools where I
want to use the comma for the CSV separator, but disabling LC_NUMERIC,
albeit better than my what I misparsed at first (forcing all locale to
'C') still looks too harsh :-\
Using -x\; looks sane and shorter tho, perhaps even -x:, to save one
extra char.
- Arnaldo
> > Completely disabling the configured locale seems too harsh to me, aren't
> > people used to changing the csv char via some option like we have in
> > 'perf stat':
> >
> > -x, --field-separator
> >
> > when changing the locale from the default 'C' one? Hey, you even used it
> > above, but you chose a CSV char that is used in this locale, oops ;-)
>
> It's just for numbers (LC_NUMERIC), everything else is still localized.
>
> -Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists