public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	eranian@hpl.hp.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] i386 add Intel PEBS and BTS cpufeature bits and detection
Date: Thu, 23 Nov 2006 17:03:47 +1100	[thread overview]
Message-ID: <6428.1164261827@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sat, 18 Nov 2006 09:24:01 BST." <200611180924.01979.ak@suse.de>

Andi Kleen (on Sat, 18 Nov 2006 09:24:01 +0100) wrote:
>On Friday 17 November 2006 23:57, Jeremy Fitzhardinge wrote:
>> Andi Kleen wrote:
>> > I have had private patches for that myself, using the MSRs on AMD
>> > and Intel.
>> >   
>> 
>> Would they be something that could be cleaned up into something
>> mergeable?  
>
>Hmm maybe.
>
>> It would be nice to have something that could be left 
>> enabled all the time, 
>
>That would add considerable latency to all exceptions.
>
>And unfortunately we take more than 16 jumps before
>we figure out an oops, so all the previous data would be gone
>if it was only done in the error path.
>
>If the CPU had a "disable LBR on exceptions" bit that would
>work. Unfortunately it hasn't.

LBR is mainly useful on wild branches to random addresses.  As such,
you really only need to disable LBR in the page fault handler.  For a
long time, KDB had LBR support with this replacement for the i386 page
fault handler.

#if defined(CONFIG_KDB)
ENTRY(page_fault_mca)
       pushl %ecx
       pushl %edx
       pushl %eax
       movl  $473,%ecx
       rdmsr
       andl  $0xfffffffe,%eax          /* Disable last branch recording */
       wrmsr
       popl  %eax
       popl  %edx
       popl  %ecx
       pushl $do_page_fault
       jmp error_code
#endif

Nobody was using the LBR feature of KDB so I removed it in 2.6.17.


  reply	other threads:[~2006-11-23  6:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 21:32 [PATCH] i386 add Intel PEBS and BTS cpufeature bits and detection Stephane Eranian
2006-11-15 21:34 ` [PATCH] x86-64 " Stephane Eranian
2006-11-16  0:18 ` [PATCH] i386 " Andrew Morton
2006-11-16 14:20 ` [PATCH] x86-64 add Intel BTS cpufeature bit and detection (take 2) Stephane Eranian
2006-11-16 14:22   ` [PATCH] i386 " Stephane Eranian
2006-11-16 14:23   ` [PATCH] x86-64 " Andi Kleen
2006-11-17  1:34 ` [PATCH] i386 add Intel PEBS and BTS cpufeature bits and detection Jeremy Fitzhardinge
2006-11-17  4:29   ` Andi Kleen
2006-11-17  7:57     ` Stephane Eranian
2006-11-17  9:22       ` Andi Kleen
2006-11-17 12:29         ` Stephane Eranian
2006-11-17 22:57     ` Jeremy Fitzhardinge
2006-11-18  8:24       ` Andi Kleen
2006-11-23  6:03         ` Keith Owens [this message]
2006-11-23  8:52           ` 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=6428.1164261827@kao2.melbourne.sgi.com \
    --to=kaos@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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