linux-kernel - Re: [PATCH 0/2] perf: Use LBR for machine/oops debugging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bd4cb8901003290616s67aac7d3jb4bec31e2c0a73d4@mail.gmail.com>
Date:	Mon, 29 Mar 2010 14:16:23 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>, mingo@...e.hu,
	Linus Torvalds <torvalds@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] perf: Use LBR for machine/oops debugging

On Mon, Mar 29, 2010 at 2:08 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Peter Zijlstra <a.p.zijlstra@...llo.nl> writes:
>
>> 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().
>
>
> die is too late. they will only contain the oops code then.
>
Most likely yes,  especially with small LBR, such as on Intel Core.


> -Andi
>
> --
> ak@...ux.intel.com -- Speaking for myself only.
>
--
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/