[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101110185213.GJ22410@elte.hu>
Date: Wed, 10 Nov 2010 19:52:13 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Borislav Petkov <bp@...en8.de>,
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
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 2010-11-10 at 18:41 +0100, Ingo Molnar wrote:
>
> > > 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.
>
> I'm not sure it needs to be small. We can have a persistent buffer that may be
> resized at any time. It can start off small, or with a kernel command line, be as
> big as you want it.
Sure.
> Basically, what ftrace has now.
>
> Also, with a way that root user can get a handle on this buffer, and just trace
> global events with it.
Yeah.
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