LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: "David Ahern" <dsahern@gmail.com>, "Jiri Olsa" <jolsa@kernel.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: heads up/RFC: 'perf trace' using ordered_events
Date: Sat, 07 Mar 2015 14:45:24 +0200	[thread overview]
Message-ID: <54FAF2E4.3030109@intel.com> (raw)
In-Reply-To: <20150304010709.GQ5187@kernel.org>

On 4/03/2015 3:07 a.m., Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 04, 2015 at 10:01:23AM +0900, Namhyung Kim escreveu:
>> On Tue, Mar 03, 2015 at 01:49:40PM -0300, Arnaldo Carvalho de Melo wrote:
>>> Hi,
>>>
>>> 	Just a preview, but this is something David had mentioned at some
>>> point, a major problem with 'perf trace' was that it wasn't using
>>> 'perf_session' event reordering mechanism, so I've been working on making it
>>> use it, refactoring the ordered_events code so that it can be used by tools
>>> that don't deal with perf.data files.
>
>> At a conceptual level, I think event processing should be done with
>> session.  Even if perf trace does not do anything with a data file it
>> can have a (live) session like perf top does.  This way we can avoid
>
> perf top is another one I want to move away from perf_session, as it
> doesn't use any perf.data file, but needs to have events ordered.
>
> But then I really need to look at what you done in your patchset,
> probably I am missing something (or a lot).

The change appears to conflict substantially with the patches I have for
adding instruction tracing support. I will send them again soon, so you
can see what I mean.

My first thought would be that iterating over events from an event
source would be the natural abstraction which would not differentiate
from where the events came. i.e. it should not matter if the back end
is a perf.data file, pipe, or mmap.

Generally there is a need for a top level data structure. It avoids having
to use global variables and reduces the number of parameters that get
passed around.


  reply	other threads:[~2015-03-07 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 16:49 Arnaldo Carvalho de Melo
2015-03-04  1:01 ` Namhyung Kim
2015-03-04  1:07   ` Arnaldo Carvalho de Melo
2015-03-07 12:45     ` Adrian Hunter [this message]
2015-03-09 13:21       ` Arnaldo Carvalho de Melo
2015-03-10  6:06         ` Namhyung Kim
2015-03-10 14:25           ` David Ahern
2015-03-11  0:33             ` 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=54FAF2E4.3030109@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --subject='Re: heads up/RFC: '\''perf trace'\'' using ordered_events' \
    /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

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).