lkml.org 
[lkml]   [2010]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC,PATCH 2/2] perf, x86: Utilize the LBRs for machine/oops debugging

* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

> The LBRs are relatively cheap to keep enabled and provide some history to
> OOPSen, also some CPUs are reported to keep them over soft-reset, which
> allows us to use them to debug things like tripple faults.
>
> Therefore introduce a boot option: lbr_debug=on, which always enable the
> LBRs and will print the LBRs on CPU init and die().

Yummie!

Have you got some sample lbr_debug=1 output as well by any chance, with a
crash provoked somewhere? How good is the output in practice? (i.e. how many
artificial entries do we have at the end of the buffer, filled with crash
related addresses?)

Also, i think we should use something more descriptive than lbr_debug=y.
Perhaps crash_trace=1 or so?

Plus, it would be nice to have a sysctl entry for this as well - so that
production systems can enable this if they want to enrich the output of some
difficult-to-analyze kernel crash, without yet another reboot.

Ingo


\
 
 \ /
  Last update: 2010-03-29 19:05    [W:0.079 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site