[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101110174122.GA4001@elte.hu>
Date: Wed, 10 Nov 2010 18:41:22 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Borislav Petkov <bp@...en8.de>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
"Luck, Tony" <tony.luck@...el.com>, linux-kernel@...r.kernel.org,
ying.huang@...el.com, 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
* Borislav Petkov <bp@...en8.de> wrote:
> On Wed, Nov 10, 2010 at 11:52:40AM -0500, Steven Rostedt wrote:
> > Also, lets not focus now on implementation. Let's try to concentrate on
> > what we want the tools to be able to do.
> >
> > For example, I would like:
> >
> > Very small entries, and pick and chose what I want in my entries.
> >
> > A way to read it fast to a file or over the network (splice).
> >
> > The read backwards seems like a cool idea, but I would not want to throw
> > away the read forwards part either.
>
> It would also be cool to be able to allocate those buffers as early as possible,
> even if before MCA is enabled, so that I won't have to copy MCE data which got
> logged before the tracing subsystem got enabled to the buffers proper.
We could even have some (small) statically enabled build-time buffer that could be
enabled straight away before any allocators are enabled.
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