From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/4] perf hist: Simplify __hpp_fmt() using hpp_fmt_data
Date: Tue, 4 Jun 2024 17:47:51 -0700 [thread overview]
Message-ID: <Zl-1t3t-3eUwDcdI@google.com> (raw)
In-Reply-To: <Zl8wVwNaKDXLTWbq@x1>
On Tue, Jun 04, 2024 at 12:18:47PM -0300, Arnaldo Carvalho de Melo wrote:
> On Mon, Jun 03, 2024 at 03:44:10PM -0700, Namhyung Kim wrote:
> > The struct hpp_fmt_data is to keep the values for each group members so
> > it doesn't need to check the event index in the group.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/ui/hist.c | 75 +++++++++++++++++++++-----------------------
> > 1 file changed, 36 insertions(+), 39 deletions(-)
> >
> > diff --git a/tools/perf/ui/hist.c b/tools/perf/ui/hist.c
> > index e30fcb1e87e7..539978c95cfd 100644
> > --- a/tools/perf/ui/hist.c
> > +++ b/tools/perf/ui/hist.c
> > @@ -46,65 +46,62 @@ static int __hpp__fmt_print(struct perf_hpp *hpp, struct hists *hists, u64 val,
> > return hpp__call_print_fn(hpp, print_fn, fmt, len, val);
> > }
> >
> > +struct hpp_fmt_data {
> > + struct hists *hists;
> > + u64 val;
> > + int samples;
> > +};
>
> Can we try to avoid vague terms like 'data' and use a hopefully more
> clear 'hpp_fmt_value' instead?
Sure, I can do that. I thought 'data' was better since it contains more
than a value like a pointer to hist and number of samples. But it's not
a big deal, and I can make the change.
>
> > static int __hpp__fmt(struct perf_hpp *hpp, struct hist_entry *he,
> > hpp_field_fn get_field, const char *fmt, int len,
> > hpp_snprint_fn print_fn, enum perf_hpp_fmt_type fmtype)
> > {
> > - int ret;
> > + int ret = 0;
> > struct hists *hists = he->hists;
> > struct evsel *evsel = hists_to_evsel(hists);
> > + struct evsel *pos;
> > char *buf = hpp->buf;
> > size_t size = hpp->size;
> > + int i, nr_members = 1;
> > + struct hpp_fmt_data *data;
>
> Here we then use:
>
> struct hpp_fmt_value *values;
Yep, will change in v3.
Thanks,
Namhyung
>
> > +
> > + if (evsel__is_group_event(evsel))
> > + nr_members = evsel->core.nr_members;
> > +
> > + data = calloc(nr_members, sizeof(*data));
> > + if (data == NULL)
> > + return 0;
>
>
> > +
> > + i = 0;
> > + for_each_group_evsel(pos, evsel)
> > + data[i++].hists = evsel__hists(pos);
> >
> > - ret = __hpp__fmt_print(hpp, hists, get_field(he), he->stat.nr_events,
> > - fmt, len, print_fn, fmtype);
> > + data[0].val = get_field(he);
> > + data[0].samples = he->stat.nr_events;
> >
> > if (evsel__is_group_event(evsel)) {
> > - int prev_idx, idx_delta;
> > struct hist_entry *pair;
> > - int nr_members = evsel->core.nr_members;
> > -
> > - prev_idx = evsel__group_idx(evsel);
> >
> > list_for_each_entry(pair, &he->pairs.head, pairs.node) {
> > - u64 period = get_field(pair);
> > - u64 total = hists__total_period(pair->hists);
> > - int nr_samples = pair->stat.nr_events;
> > -
> > - if (!total)
> > - continue;
> > + for (i = 0; i < nr_members; i++) {
> > + if (data[i].hists != pair->hists)
> > + continue;
> >
> > - evsel = hists_to_evsel(pair->hists);
> > - idx_delta = evsel__group_idx(evsel) - prev_idx - 1;
> > -
> > - while (idx_delta--) {
> > - /*
> > - * zero-fill group members in the middle which have
> > - * no samples, pair->hists is not correct but it's
> > - * fine since the value is 0.
> > - */
> > - ret += __hpp__fmt_print(hpp, pair->hists, 0, 0,
> > - fmt, len, print_fn, fmtype);
> > + data[i].val = get_field(pair);
> > + data[i].samples = pair->stat.nr_events;
> > + break;
> > }
> > -
> > - ret += __hpp__fmt_print(hpp, pair->hists, period, nr_samples,
> > - fmt, len, print_fn, fmtype);
> > -
> > - prev_idx = evsel__group_idx(evsel);
> > }
> > + }
> >
> > - idx_delta = nr_members - prev_idx - 1;
> > -
> > - while (idx_delta--) {
> > - /*
> > - * zero-fill group members at last which have no sample.
> > - * the hists is not correct but it's fine like above.
> > - */
> > - ret += __hpp__fmt_print(hpp, evsel__hists(evsel), 0, 0,
> > - fmt, len, print_fn, fmtype);
> > - }
> > + for (i = 0; i < nr_members; i++) {
> > + ret += __hpp__fmt_print(hpp, data[i].hists, data[i].val,
> > + data[i].samples, fmt, len,
> > + print_fn, fmtype);
> > }
> >
> > + free(data);
> > +
> > /*
> > * Restore original buf and size as it's where caller expects
> > * the result will be saved.
> > --
> > 2.45.1.288.g0e0cd299f1-goog
next prev parent reply other threads:[~2024-06-05 0:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 22:44 [PATCH 0/4] perf report: Omit dummy events in the output (v2) Namhyung Kim
2024-06-03 22:44 ` [PATCH 1/4] perf hist: Factor out __hpp__fmt_print() Namhyung Kim
2024-06-04 15:07 ` Arnaldo Carvalho de Melo
2024-06-05 0:42 ` Namhyung Kim
2024-06-03 22:44 ` [PATCH 2/4] perf hist: Simplify __hpp_fmt() using hpp_fmt_data Namhyung Kim
2024-06-04 15:18 ` Arnaldo Carvalho de Melo
2024-06-05 0:47 ` Namhyung Kim [this message]
2024-06-03 22:44 ` [PATCH 3/4] perf hist: Add symbol_conf.skip_empty Namhyung Kim
2024-06-03 22:44 ` [PATCH 4/4] perf hist: Honor symbol_conf.skip_empty Namhyung Kim
2024-06-04 15:24 ` [PATCH 0/4] perf report: Omit dummy events in the output (v2) Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2024-06-07 20:29 [PATCH 0/4] perf report: Omit dummy events in the output (v3) Namhyung Kim
2024-06-07 20:29 ` [PATCH 2/4] perf hist: Simplify __hpp_fmt() using hpp_fmt_data Namhyung Kim
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=Zl-1t3t-3eUwDcdI@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.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=mingo@kernel.org \
--cc=peterz@infradead.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).