Re: [PATCH 00/18] perf metric: Add support to reuse metric

[Jiri Olsa]

On Thu, Jul 16, 2020 at 01:32:04PM +0200, Jiri Olsa wrote:

SNIP

> > > ---
> > > Jiri Olsa (18):
> > >        perf metric: Rename expr__add_id to expr__add_val
> > >        perf metric: Add struct expr_id_data to keep expr value
> > >        perf metric: Add expr__add_id function
> > >        perf metric: Change expr__get_id to return struct expr_id_data
> > >        perf metric: Add expr__del_id function
> > >        perf metric: Add find_metric function
> > >        perf metric: Add add_metric function
> > >        perf metric: Rename __metricgroup__add_metric to __add_metric
> > >        perf metric: Collect referenced metrics in struct metric_ref_node
> > >        perf metric: Collect referenced metrics in struct metric_expr
> > >        perf metric: Add referenced metrics to hash data
> > >        perf metric: Compute referenced metrics
> > >        perf metric: Add events for the current group
> > >        perf metric: Add cache_miss_cycles to metric parse test
> > >        perf metric: Add DCache_L2 to metric parse test
> > >        perf metric: Add recursion check when processing nested metrics
> > >        perf metric: Rename struct egroup to metric
> > >        perf metric: Rename group_list to list
> > 
> > I was thinking that a test metric using this reuse feature could be added in
> > pmu-events/arch/test/test_cpu. But since no relevant parsing is done in
> > jevents, maybe not a lot of value. Just for a bit more completeness.
> 
> ok, I think it's a good idea

actually those tests treats all IDs in metrics as events,
so what will happen is that the nested metric ID will be
considered as event with assigned value

so I don't see too much value to add nested metrics there,
I think tests/parse-metric.c will cover all metrics usage

jirka