[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1339671367.2559.29.camel@twins>
Date: Thu, 14 Jun 2012 12:56:07 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Stephane Eranian <eranian@...gle.com>
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, 2012-06-14 at 12:50 +0200, Peter Zijlstra wrote:
> On Thu, 2012-06-14 at 12:45 +0200, Stephane Eranian wrote:
> > > 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.
>
> Right.. but if you leave the old stuff in for say 2 years and start
> emitting a warning on using the old stuff after 1 year.. give or take a
> few years we should be able to get the old stuff deprecated and removed.
Another thing I did consider was trying to JIT a whole output path in
order to reduce the insane amount of conditionals in there. It would be
very nice if GCC grew something to help stitch code snippets together so
we could write it arch independent.
--
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