From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 1/3] perf script: Remove default_scripting_ops
Date: Thu, 26 Nov 2015 13:33:47 -0300 [thread overview]
Message-ID: <20151126163347.GB28162@kernel.org> (raw)
In-Reply-To: <1448546125-29245-1-git-send-email-jolsa@kernel.org>
Em Thu, Nov 26, 2015 at 02:55:23PM +0100, Jiri Olsa escreveu:
> The default script handler (the one that displays samples on screen)
> is implemented scripting_ops instance with process_event callback.
>
> This way we can't pass any script config into display function,
> because we don't want perl or python handlers to be depended on
> perf script internals.
>
> Removing the default_scripting_ops and calling process event
> function directly. This way it's possible to pass perf_script
> struct and process configuration data in following commit.
>
> Link: http://lkml.kernel.org/n/tip-emel4exb5d0930e3h588iidi@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Applied, with David's ack.
- Arnaldo
next prev parent reply other threads:[~2015-11-26 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 13:55 [PATCH 1/3] perf script: Remove default_scripting_ops Jiri Olsa
2015-11-26 13:55 ` [PATCH 2/3] perf script: Pass perf_script into process_event Jiri Olsa
2015-11-26 16:22 ` Arnaldo Carvalho de Melo
2015-11-26 17:55 ` [PATCHv2 " Jiri Olsa
2015-11-27 7:45 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-11-26 13:55 ` [PATCH 3/3] perf script: Align event name properly Jiri Olsa
2015-11-26 14:25 ` David Ahern
2015-11-26 14:30 ` Jiri Olsa
2015-11-26 14:34 ` David Ahern
2015-12-27 11:59 ` Jiri Olsa
2015-11-26 16:33 ` Arnaldo Carvalho de Melo [this message]
2015-11-27 7:43 ` [tip:perf/core] perf script: Remove default_scripting_ops tip-bot for 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=20151126163347.GB28162@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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