From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, eranian@google.com,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/4] perf, tools, stat: Abstract stat metrics printing
Date: Sat, 8 Aug 2015 19:40:32 +0200 [thread overview]
Message-ID: <20150808174032.GF17040@krava.brq.redhat.com> (raw)
In-Reply-To: <20150804004111.GV1747@two.firstfloor.org>
On Tue, Aug 04, 2015 at 02:41:11AM +0200, Andi Kleen wrote:
> >
> > because we already need to make the print_metric callback global,
> > would it be better to make this struct global, having all the
> > needed callbacks defined within? something like:
>
> It's actually not global, but static.
>
> I skipped this change. After some other changes there is only
> a single function call with these arguments left, so it's not
> an issue to pass it around.
hum, I dont understand.. I can se the same code in the new version:
+typedef void (*print_metric_t)(void *ctx, const char *color, const char *unit,
+ const char *fmt, double val);
+
void perf_stat__reset_shadow_stats(void);
void perf_stat__update_shadow_stats(struct perf_evsel *counter, u64 *count,
int cpu);
-void perf_stat__print_shadow_stats(FILE *out, struct perf_evsel *evsel,
- double avg, int cpu, enum aggr_mode aggr);
+void perf_stat__print_shadow_stats(struct perf_evsel *evsel,
+ double avg, int cpu,
+ print_metric_t print_metric,
+ void (*new_line)(void *ctx),
+ void *ctx);
both:
print_metric_t print_metric
void (*new_line)(void *ctx)
are still there.. what single function call did you mean?
jirka
next prev parent reply other threads:[~2015-08-08 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 0:21 perf, tools: Refactor and support interval and CSV metrics Andi Kleen
2015-07-30 0:21 ` [PATCH 1/4] perf, tools: Do not include escape sequences in color_vfprintf return Andi Kleen
2015-07-30 12:35 ` [PATCH] perf tools: Remove color_fprintf_ln function Jiri Olsa
2015-07-30 0:21 ` [PATCH 2/4] perf, tools, stat: Abstract stat metrics printing Andi Kleen
2015-07-30 13:42 ` Jiri Olsa
2015-07-30 13:47 ` Jiri Olsa
2015-08-04 0:41 ` Andi Kleen
2015-08-08 17:40 ` Jiri Olsa [this message]
2015-07-30 0:21 ` [PATCH 3/4] perf, tools, stat: Add support for metrics in interval mode Andi Kleen
2015-07-30 13:53 ` Jiri Olsa
2015-07-30 0:21 ` [PATCH 4/4] perf, tools, stat: Implement CSV metrics output Andi Kleen
2015-07-30 14:06 ` Jiri Olsa
2015-07-30 14:08 ` Jiri Olsa
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=20150808174032.GF17040@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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