All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Arun Kalyanasundaram <arunkaly@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"David S . Miller" <davem@davemloft.net>,
	SeongJae Park <sj38.park@gmail.com>,
	David Carrillo-Cisneros <davidcc@google.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/5] perf script python: Provide perf_sample dict to all handlers
Date: Fri, 21 Jul 2017 14:11:36 -0300	[thread overview]
Message-ID: <20170721171136.GO4134@kernel.org> (raw)
In-Reply-To: <CAGjB_BqWXsbWTnkUj=EyHrHKCt35TaSY9+ZYto4VTW1w0wKYTg@mail.gmail.com>

Em Fri, Jul 21, 2017 at 09:51:31AM -0700, Arun Kalyanasundaram escreveu:
> My apologies. Yes, I did make a couple of changes to the patch. I was
> not sure if I should be sending a v2 since the previous one was a rfc.
> Please ignore this patch, I will resend this highlighting the new
> changes made.

Thanks a lot! It takes some time to get the whole process going
smoothly, but we'll get there :-)

- Arnaldo
 
> On Fri, Jul 21, 2017 at 9:28 AM, Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> > Em Fri, Jul 21, 2017 at 09:46:39AM +0200, Jiri Olsa escreveu:
> >> On Thu, Jul 20, 2017 at 07:01:13PM -0700, Arun Kalyanasundaram wrote:
> >> > The process_event python hook receives a dict with most perf_sample
> >> > entries.
> >>
> >> hi,
> >> was there any change to the rfc post?
> >
> > I was wondering that, please stick a v1, v2, etc to the subject, and
> > state the changes across versions, to make things clear.
> >
> > - Arnaldo
> >
> >> thanks,
> >> jirka
> >>
> >> >
> >> > Other handlers (e.g. trace_unhandled, python_process_tracepoint) predate
> >> > the introduction of this dict and do not receive it. This patch series
> >> > adds the dict to all handlers, aiming to unify the information passed to
> >> > them.
> >> >
> >> > This change adds an additional argument to the affected handlers. To
> >> > keep backwards compatibility (and avoid unnecessary work), do not pass
> >> > the aforementioned dict if the number of arguments signals that handler
> >> > version predates this change.
> >> >
> >> > In addition, provide time_enabled, time_running and counter value in the
> >> > perf_sample dict.
> >> >
> >> > Initial Discussion: https://lkml.org/lkml/2017/7/1/108
> >> >
> >> > Arun Kalyanasundaram (5):
> >> >   perf script python: Allocate memory only if handler exists
> >> >   perf script python: Refactor creation of perf sample dict
> >> >   perf script python: Add sample_read to dict
> >> >   perf script python: Add perf_sample dict to tracepoint handlers
> >> >   perf script python: Generate hooks with additional argument
> >> >
> >> >  .../util/scripting-engines/trace-event-python.c    | 246 +++++++++++++++------
> >> >  1 file changed, 184 insertions(+), 62 deletions(-)
> >> >
> >> > --
> >> > 2.14.0.rc0.284.gd933b75aa4-goog
> >> >

      reply	other threads:[~2017-07-21 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  2:01 [PATCH 0/5] perf script python: Provide perf_sample dict to all handlers Arun Kalyanasundaram
2017-07-21  2:01 ` [PATCH 1/5] perf script python: Allocate memory only if handler exists Arun Kalyanasundaram
2017-07-21  2:01 ` [PATCH 2/5] perf script python: Refactor creation of perf sample dict Arun Kalyanasundaram
2017-07-21  2:01 ` [PATCH 3/5] perf script python: Add sample_read to dict Arun Kalyanasundaram
2017-07-21  2:01 ` [PATCH 4/5] perf script python: Add perf_sample dict to tracepoint handlers Arun Kalyanasundaram
2017-07-21  2:01 ` [PATCH 5/5] perf script python: Generate hooks with additional argument Arun Kalyanasundaram
2017-07-21  7:46 ` [PATCH 0/5] perf script python: Provide perf_sample dict to all handlers Jiri Olsa
2017-07-21 16:28   ` Arnaldo Carvalho de Melo
2017-07-21 16:51     ` Arun Kalyanasundaram
2017-07-21 17:11       ` 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=20170721171136.GO4134@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arunkaly@google.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=davidcc@google.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sj38.park@gmail.com \
    /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.