[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211007110543.564963-1-james.clark@arm.com>
Date: Thu, 7 Oct 2021 12:05:39 +0100
From: James Clark <james.clark@....com>
To: acme@...nel.org, john.garry@...wei.com, ak@...ux.intel.com,
linux-perf-users@...r.kernel.org
Cc: Nick.Forrington@....com, Andrew.Kilroy@....com,
James Clark <james.clark@....com>,
Will Deacon <will@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] perf tools: Enable strict JSON parsing
After a discussion on "[PATCH 1/4] perf vendor events: Syntax corrections in Neoverse N1 json",
John Garry suggested that we can just modify the parser to make it more strict. Hopefully this will
remove the need to apply any future JSON comma fixup commits.
Applies on top of "[PATCH v2 1/3] perf vendor events: Syntax corrections in Neoverse N1 json" on
perf/core.
Also available at:
git clone --branch james-json-parse-fix git@....gitlab.arm.com:linux-arm/linux-jc.git
James Clark (3):
perf vendor-events: Fix all remaining invalid JSON files
perf tools: Make the JSON parser more conformant when in strict mode
perf tools: Enable strict JSON parsing
.../arch/arm64/ampere/emag/bus.json | 2 +-
.../arch/arm64/ampere/emag/cache.json | 20 ++++-----
.../arch/arm64/ampere/emag/clock.json | 2 +-
.../arch/arm64/ampere/emag/exception.json | 4 +-
.../arch/arm64/ampere/emag/instruction.json | 10 ++---
.../arch/arm64/ampere/emag/memory.json | 4 +-
.../arch/arm64/hisilicon/hip08/metrics.json | 2 +-
.../pmu-events/arch/nds32/n13/atcpmu.json | 2 +-
.../pmu-events/arch/s390/cf_z10/basic.json | 2 +-
.../pmu-events/arch/s390/cf_z10/crypto.json | 2 +-
.../pmu-events/arch/s390/cf_z10/extended.json | 2 +-
.../pmu-events/arch/s390/cf_z13/basic.json | 2 +-
.../pmu-events/arch/s390/cf_z13/crypto.json | 2 +-
.../pmu-events/arch/s390/cf_z13/extended.json | 2 +-
.../pmu-events/arch/s390/cf_z14/basic.json | 2 +-
.../pmu-events/arch/s390/cf_z14/crypto.json | 2 +-
.../pmu-events/arch/s390/cf_z14/extended.json | 2 +-
.../pmu-events/arch/s390/cf_z15/basic.json | 2 +-
.../pmu-events/arch/s390/cf_z15/crypto.json | 2 +-
.../pmu-events/arch/s390/cf_z15/crypto6.json | 2 +-
.../pmu-events/arch/s390/cf_z15/extended.json | 2 +-
.../pmu-events/arch/s390/cf_z196/basic.json | 2 +-
.../pmu-events/arch/s390/cf_z196/crypto.json | 2 +-
.../arch/s390/cf_z196/extended.json | 2 +-
.../pmu-events/arch/s390/cf_zec12/basic.json | 2 +-
.../pmu-events/arch/s390/cf_zec12/crypto.json | 2 +-
.../arch/s390/cf_zec12/extended.json | 2 +-
.../arch/test/test_soc/cpu/uncore.json | 2 +-
.../arch/x86/icelakex/icx-metrics.json | 2 +-
tools/perf/pmu-events/jsmn.c | 43 ++++++++++++++++++-
30 files changed, 85 insertions(+), 46 deletions(-)
--
2.28.0
Powered by blists - more mailing lists