Re: [RFC PATCH v10 3/8] perf stat: Fork and launch perf record when perf stat needs to get retire latency value for a metric.

[Namhyung Kim]

On Tue, Jun 04, 2024 at 08:00:26PM +0000, Wang, Weilin wrote:

> > On Thu, May 30, 2024 at 11:46 PM Wang, Weilin <weilin.wang@xxxxxxxxx>
> > > > > +       /*
> > > > > +        * Only set retire_latency value to the first CPU and thread.
> > > > > +        */
> > > > > +       if (cpu_map_idx == 0 && thread == 0) {
> > > > > +       /* Lost precision when casting from double to __u64. Any
> > > > improvement? */
> > > >
> > > > As I said before I think you can set t->val * 1000 and then
> > > > set the evsel->scale to 1e3 or 1e-3.
> > >
> > > Hi Namhyung,
> > >
> > > Sorry if this is a repeated message. I thought I replied to your suggestion
> > > on this last time. I'm thinking we should keep it like this for now and make
> > > this change unless we find the precision loss is critical. Because I thought
> > > we don't want to add special code to handle the calculation and final print
> > > to keep code simple.
> > >
> > > I kept this comment here so that we don't forget about it. Please let me
> > > know if you'd like me to remove it.
> > 
> > Please see print_counter_aggrdata().  It's the generic code to print
> > the event value and it'll display the value multiplied by the scale
> > (default to 1.0).  So you can keep precision as long as you set the
> > scale properly (1e-3).
> 
> I could see the retire_latency is printed correctly after set the evsel->scale to 1e-3
> and multiply the t->val * 1000. However, this scale is not used in metric calculations. 
> We need to add code in metric calculation or display part to scale it as well. Is that 
> acceptable or do you have other suggestions? 

Hmm.. I don't know if other metric already dealt with the scale like with
RAPL events.. If not, I think it's reasonable to add that to the metric
calculation.

Ian, what do you think?

Thanks,
Namhyung