All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andrew Vagin <avagin@openvz.org>, Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] perf: create a helper structure perf_event_context
Date: Tue, 21 Aug 2012 10:14:51 -0300	[thread overview]
Message-ID: <20120821131451.GA7162@infradead.org> (raw)
In-Reply-To: <20120821095920.GA3241@gmail.com>

Em Tue, Aug 21, 2012 at 11:59:20AM +0200, Ingo Molnar escreveu:
> * Andrew Vagin <avagin@openvz.org> wrote:
> >  18 files changed, 222 insertions(+), 255 deletions(-)
> > -static int process_sample_event(struct perf_tool *tool,
> > -				union perf_event *event,
> > -				struct perf_sample *sample,
> > -				struct perf_evsel *evsel,
> > -				struct machine *machine)
> > +static int process_sample_event(struct perf_event_context *ectx)
> >  {
> > -	struct perf_annotate *ann = container_of(tool, struct perf_annotate, tool);
> > +	struct perf_sample *sample = ectx->sample;
> > +	struct perf_annotate *ann = container_of(ectx->tool, struct perf_annotate, tool);
> >  	struct addr_location al;
> 
> that looks like a nice cleanliness win.
> 
> Acked-by: Ingo Molnar <mingo@kernel.org>

I don't like it, in most cases it just moves variables from the function
signature to the start of the function.

I do agree tho that we should reduce the number of parameters as much as
we can, as I did removing that pevent one that we used to look up
event_format from the sample ID, that just was not natural as we already
had the evsel and did the lookup when reading the perf.data headers, so
it was just a matter of linking evsel to event_format at that point and
remove the pevent parameter and eliminate the needless relookups, see:

 "perf evsel: Cache associated event_format"
 fcf65bf149afa91b875ffde4455967cb63ee0be9

In the above function signature there is already room for tool specific
state in perf_tool/container_of, the other parameters are per event
natural objects.

- Arnaldo

      reply	other threads:[~2012-08-21 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 15:23 [PATCH] perf: create a helper structure perf_event_context Andrew Vagin
2012-08-21  9:59 ` Ingo Molnar
2012-08-21 13:14   ` Arnaldo Carvalho de Melo [this message]

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=20120821131451.GA7162@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=avagin@openvz.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.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.