From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [RFC,PATCH 2/2] perf, x86: Utilize the LBRs for machine/oops debugging
Date: Fri, 2 Apr 2010 22:44:46 +0200 [thread overview]
Message-ID: <20100402204446.GD21840@elte.hu> (raw)
In-Reply-To: <1269882768.12097.365.camel@laptop>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, 2010-03-29 at 19:02 +0200, Ingo Molnar wrote:
>
> > 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.
>
> Right, could do, but once it crashed it clearly to late to enable anything
> ;-)
No. What i mean is that with your patch, a debugging session would go like
this:
< kernel crashes > # reboot #1
< admin logs in and scratches head >
< admin consults kernel hackers and enables lbr_debug=1 in /etc/grub.conf >
< admin reboots > # reboot #2
< kernel crashes again > # reboot #3
With the sysctl we'd have one reboot less:
< kernel crashes > # reboot #1
< admin logs in and scratches head >
< admin consults kernel hackers and tweaks /proc/sys/kernel/x86/lbr_debug >
< kernel crashes again > # reboot #2
Thanks,
Ingo
next prev parent reply other threads:[~2010-04-02 20:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 12:20 [PATCH 0/2] perf: Use LBR for machine/oops debugging Peter Zijlstra
2010-03-29 12:20 ` [PATCH 1/2] perf, x86: fix __initconst vs const Peter Zijlstra
2010-03-29 12:20 ` [RFC,PATCH 2/2] perf, x86: Utilize the LBRs for machine/oops debugging Peter Zijlstra
2010-03-29 12:47 ` Stephane Eranian
2010-03-29 14:13 ` Peter Zijlstra
2010-03-29 14:20 ` Stephane Eranian
2010-03-29 17:02 ` Ingo Molnar
2010-03-29 17:12 ` Peter Zijlstra
2010-04-02 20:44 ` Ingo Molnar [this message]
2010-03-29 13:08 ` [PATCH 0/2] perf: Use LBR " Andi Kleen
2010-03-29 13:16 ` Stephane Eranian
2010-03-29 14:14 ` Peter Zijlstra
2010-03-29 20:09 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100402204446.GD21840@elte.hu \
--to=mingo@elte.hu \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox