[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101110174852.GB4001@elte.hu>
Date: Wed, 10 Nov 2010 18:48:52 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Steven Rostedt <rostedt@...dmis.org>,
"Luck, Tony" <tony.luck@...el.com>, linux-kernel@...r.kernel.org,
ying.huang@...el.com, bp@...en8.de, tglx@...utronix.de,
akpm@...ux-foundation.org, mchehab@...hat.com,
Frédéric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Arjan van de Ven <arjan@...radead.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [RFC/Requirements/Design] h/w error reporting
* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> On Wed, 2010-11-10 at 10:09 -0500, Steven Rostedt wrote:
> >
> > > sure the second way is the only way out, but you still need to come up with a
> > > trace data format and a control ABI.
> >
> > Great! Let's start with that then. Could you list some of the basic needs of
> > perf?
>
> Needs for what? I've already got a full control ABI and I can already redirect
> output to other buffers ;-)
Yep. The obvious direction is to extend the event buffering ABI we already have,
with whatever additions that are needed:
- document that we already support flight recorder mode
- a more compressed record format
- NOP filler events up to page boundary, for better splice and for better flight
recorder
- splice support
etc. That's how it evolved until now and it's all very extensible.
Steve, could you please list the additions you have in mind, in order of priority?
Thanks,
Ingo
--
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