From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ravi Bangoria <ravi.bangoria@amd.com>, acme@kernel.org
Cc: jolsa@kernel.org, irogers@google.com, peterz@infradead.org,
rrichter@amd.com, mingo@redhat.com, mark.rutland@arm.com,
namhyung@kernel.org, tglx@linutronix.de, bp@alien8.de,
james.clark@arm.com, leo.yan@linaro.org, ak@linux.intel.com,
eranian@google.com, like.xu.linux@gmail.com, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
sandipan.das@amd.com, ananth.narayan@amd.com,
kim.phillips@amd.com, santosh.shukla@amd.com
Subject: Re: [PATCH v5 3/8] perf headers: Pass "cpu" pmu name while printing caps
Date: Wed, 1 Jun 2022 09:35:53 -0400 [thread overview]
Message-ID: <2adf5485-db22-8dde-9d32-6615e6346c6f@linux.intel.com> (raw)
In-Reply-To: <20220601032608.1034-4-ravi.bangoria@amd.com>
On 5/31/2022 11:26 PM, Ravi Bangoria wrote:
> Avoid unnecessary conditional code to check if pmu name is NULL
> or not by passing "cpu" pmu name to the printing function.
>
> Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com>
Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Thanks,
Kan
> ---
> tools/perf/util/header.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index 53332da100e8..ee7ccd94e272 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -2058,17 +2058,11 @@ static void print_per_cpu_pmu_caps(FILE *fp, int nr_caps, char *cpu_pmu_caps,
> char *str, buf[128];
>
> if (!nr_caps) {
> - if (!pmu_name)
> - fprintf(fp, "# cpu pmu capabilities: not available\n");
> - else
> - fprintf(fp, "# %s pmu capabilities: not available\n", pmu_name);
> + fprintf(fp, "# %s pmu capabilities: not available\n", pmu_name);
> return;
> }
>
> - if (!pmu_name)
> - scnprintf(buf, sizeof(buf), "# cpu pmu capabilities: ");
> - else
> - scnprintf(buf, sizeof(buf), "# %s pmu capabilities: ", pmu_name);
> + scnprintf(buf, sizeof(buf), "# %s pmu capabilities: ", pmu_name);
>
> delimiter = buf;
>
> @@ -2085,7 +2079,7 @@ static void print_per_cpu_pmu_caps(FILE *fp, int nr_caps, char *cpu_pmu_caps,
> static void print_cpu_pmu_caps(struct feat_fd *ff, FILE *fp)
> {
> print_per_cpu_pmu_caps(fp, ff->ph->env.nr_cpu_pmu_caps,
> - ff->ph->env.cpu_pmu_caps, NULL);
> + ff->ph->env.cpu_pmu_caps, (char *)"cpu");
> }
>
> static void print_hybrid_cpu_pmu_caps(struct feat_fd *ff, FILE *fp)
next prev parent reply other threads:[~2022-06-01 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 3:26 [PATCH v5 0/8] perf/amd: Zen4 IBS extensions support (tool changes) Ravi Bangoria
2022-06-01 3:26 ` [PATCH v5 1/8] perf record ibs: Warn about sampling period skew Ravi Bangoria
2022-06-02 20:30 ` Namhyung Kim
2022-06-03 5:12 ` Ravi Bangoria
2022-06-03 5:28 ` Ravi Bangoria
2022-06-03 19:25 ` Arnaldo Carvalho de Melo
2022-06-01 3:26 ` [PATCH v5 2/8] perf tool: Parse pmu caps sysfs only once Ravi Bangoria
2022-06-01 13:35 ` Liang, Kan
2022-06-01 13:51 ` Ravi Bangoria
2022-06-01 13:55 ` Liang, Kan
2022-06-01 3:26 ` [PATCH v5 3/8] perf headers: Pass "cpu" pmu name while printing caps Ravi Bangoria
2022-06-01 13:35 ` Liang, Kan [this message]
2022-06-01 3:26 ` [PATCH v5 4/8] perf headers: Store pmu caps in an array of strings Ravi Bangoria
2022-06-01 13:36 ` Liang, Kan
2022-06-02 21:37 ` Namhyung Kim
2022-06-03 5:20 ` Ravi Bangoria
2022-06-01 3:26 ` [PATCH v5 5/8] perf headers: Record non-cpu pmu capabilities Ravi Bangoria
2022-06-01 13:37 ` Liang, Kan
2022-06-01 13:58 ` Liang, Kan
2022-06-01 3:26 ` [PATCH v5 6/8] perf/x86/ibs: Add new IBS register bits into header Ravi Bangoria
2022-06-02 21:48 ` Namhyung Kim
2022-06-03 5:24 ` Ravi Bangoria
2022-06-01 3:26 ` [PATCH v5 7/8] perf tool ibs: Sync amd ibs header file Ravi Bangoria
2022-06-01 3:26 ` [PATCH v5 8/8] perf script ibs: Support new IBS bits in raw trace dump Ravi Bangoria
2022-06-01 14:04 ` [PATCH v5 0/8] perf/amd: Zen4 IBS extensions support (tool changes) Liang, Kan
2022-06-01 14:10 ` Ravi Bangoria
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=2adf5485-db22-8dde-9d32-6615e6346c6f@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kim.phillips@amd.com \
--cc=leo.yan@linaro.org \
--cc=like.xu.linux@gmail.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=ravi.bangoria@amd.com \
--cc=rrichter@amd.com \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).