[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBT54L=CuC_gJF3dnOOn6Tr1adVtedLOgzZQbmpZ5B-szA@mail.gmail.com>
Date: Thu, 14 Jun 2012 12:45:15 +0200
From: Stephane Eranian <eranian@...gle.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Jiri Olsa <jolsa@...hat.com>, acme@...hat.com, mingo@...e.hu,
paulus@...ba.org, cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com,
gorcunov@...nvz.org, tzanussi@...il.com, mhiramat@...hat.com,
robert.richter@....com, fche@...hat.com,
linux-kernel@...r.kernel.org, masami.hiramatsu.pt@...achi.com,
drepper@...il.com, asharma@...com, benjamin.redelings@...cent.org
Subject: Re: [PATCH 02/19] perf: Add ability to attach user level registers
dump to sample
On Thu, Jun 14, 2012 at 10:36 AM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Wed, 2012-06-13 at 15:41 +0200, Stephane Eranian wrote:
>> Ok, yes that one. It would have been much nicer to follow the enum
>> order.
>
> Yes.. I should make a list of all the things we should've done
> differently. Maybe if that list grows long enough someone gets motivated
> enough to rev the format as a whole.
>
Yeah, that would be good.
I will soon post a patch to extend that format to make it possible to
have distinct sample_type per event and yet be able to parse them.
I am still waiting for Arnaldo to take my perf patches concerning pipe
mode first. Can't have too many patch sets in flight at the same time.
> It would be a tedious endeavour since you'd need to have both output
> paths available for a good while, but it might be worth it in the long
> run depending on how painful the current format becomes.
True. What we don't know however, it how many other tools are out
there using the kernel API directly.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists