> > amdzen2/core.json had a trailing comma on the x_ret_fus_brnch_inst
> > event. Since that goes against the JSON standard, lets remove it.
>
> is this the only case in all the .json files we have in
> tools/perf/pmu-events/?
I just searched the pmu-events/arch/ folder, and found one other instance in
amdzen1. I'll send an updated patch now.
>
> - Arnaldo
>
> > Signed-off-by: Henry Burns <henrywolfebu...@gmail.com>
> > ---
> > tools/perf/pmu-events/arch/x86/amdzen2/core.json | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/pmu-events/arch/x86/amdzen2/core.json
> > b/tools/perf/pmu-events/arch/x86/amdzen2/core.json
> > index de89e5a44ff1..4b75183da94a 100644
> > --- a/tools/perf/pmu-events/arch/x86/amdzen2/core.json
> > +++ b/tools/perf/pmu-events/arch/x86/amdzen2/core.json
> > @@ -125,6 +125,6 @@
> > {
> > "EventName": "ex_ret_fus_brnch_inst",
> > "EventCode": "0x1d0",
> > - "BriefDescription": "Retired Fused Instructions. The number of
> > fuse-branch instructions retired per cycle. The number of events logged per
> > cycle can vary from 0-8.",
> > + "BriefDescription": "Retired Fused Instructions. The number of
> > fuse-branch instructions retired per cycle. The number of events logged per
> > cycle can vary from 0-8."
> > }
> > ]
> > --
> > 2.25.1
> >
>
> --
>
> - Arnaldo
