From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Rob Herring <robh@kernel.org>, James Clark <james.clark@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/3] perf list/debug output fixes
Date: Thu, 31 Aug 2023 00:14:18 -0700 [thread overview]
Message-ID: <20230831071421.2201358-1-irogers@google.com> (raw)
Fix a long standing parse_events_term cloning bug so that the bad
display of terms can be fixed and the code somewhat more intuitive:
https://lore.kernel.org/lkml/20230830070753.1821629-2-irogers@google.com/
Fix a bug caused by the rename of 'cpu' to 'default_core' in perf list.
Add more documentation, increase type safety and fix some related bugs
where terms weren't initialized properly.
Ian Rogers (3):
perf list: Don't print Unit for default_core
perf parse-events: Name the two term enums
perf parse-events: Fix propagation of term's no_value when cloning
tools/perf/builtin-list.c | 2 +-
tools/perf/util/parse-events.c | 203 +++++++++++++++++++++++----------
tools/perf/util/parse-events.h | 60 +++++++---
tools/perf/util/parse-events.l | 2 +-
tools/perf/util/parse-events.y | 27 +++--
tools/perf/util/pmu.c | 2 +-
6 files changed, 207 insertions(+), 89 deletions(-)
--
2.42.0.rc2.253.gd59a3bf2b4-goog
next reply other threads:[~2023-08-31 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 7:14 Ian Rogers [this message]
2023-08-31 7:14 ` [PATCH v1 1/3] perf list: Don't print Unit for default_core Ian Rogers
2023-08-31 7:14 ` [PATCH v1 2/3] perf parse-events: Name the two term enums Ian Rogers
2023-08-31 7:14 ` [PATCH v1 3/3] perf parse-events: Fix propagation of term's no_value when cloning Ian Rogers
2023-08-31 18:28 ` [PATCH v1 0/3] perf list/debug output fixes Liang, Kan
2023-08-31 18:41 ` Ian Rogers
2023-08-31 19:25 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230831071421.2201358-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.