All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jan Beulich <JBeulich@novell.com>,
	"H. Peter Anvin" <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Soeren Sandmann Pedersen <sandmann@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC PATCH 1/2] x86: Fix rbp saving in pt_regs on irq entry
Date: Fri, 7 Jan 2011 18:17:09 +0100	[thread overview]
Message-ID: <20110107171707.GC3066@nowhere> (raw)
In-Reply-To: <20110107165843.GA7376@elte.hu>

On Fri, Jan 07, 2011 at 05:58:43PM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > On Fri, Jan 07, 2011 at 04:13:58PM +0000, Jan Beulich wrote:
> > > >>> On 07.01.11 at 17:05, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > > > Once I'll have perf callchain based on CFI ready, we'll perhaps find some 
> > > > issues
> > > > there. Although I guess there are already tools that can make use of that.
> > > 
> > > Is this to read that you're planning to do a re-spin of the CFI
> > > unwinding code (which I'm not allowed to submit another time,
> > > but which we've been using for years in SuSE distros) then?
> > 
> > An in-kernel CFI unwinder?
> > 
> > No the intended CFI unwinding that I'm working on for perf is made
> > on post-processing, on top of partial stack and regs snapshots.
> > 
> > The true unwinding is computed in userspace.
> 
> I think that design will be fundamentally more robust and more flexible than an 
> in-kernel unwinder.

But in fact for the kernel unwinding it still uses frame pointers which is certainly
the fastest and lightest way to unwind a stack. Very nice for our profiling.

Now one may argue about the loss of a register and its associated overhead, not
sure it's always noticeable though...

  reply	other threads:[~2011-01-07 17:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 14:51 [RFC GIT PULL] perf updates Frederic Weisbecker
2011-01-06 14:51 ` [PATCH 2/2] perf: Build tools with frame pointer Frederic Weisbecker
2011-01-07 15:31   ` [tip:perf/core] perf tools: Build " tip-bot for Frederic Weisbecker
     [not found] ` <1294325513-14276-2-git-send-email-fweisbec@gmail.com>
2011-01-06 15:18   ` [RFC PATCH 1/2] x86: Fix rbp saving in pt_regs on irq entry Jan Beulich
2011-01-06 15:45     ` Frederic Weisbecker
2011-01-06 16:10       ` Jan Beulich
2011-01-06 16:22         ` Frederic Weisbecker
2011-01-06 16:39           ` Jan Beulich
2011-01-06 16:54             ` Frederic Weisbecker
2011-01-06 16:58               ` Jan Beulich
2011-01-06 17:12                 ` Frederic Weisbecker
2011-01-06 17:24                   ` Frederic Weisbecker
2011-01-07  7:45                   ` Jan Beulich
2011-01-07 12:31                     ` Ingo Molnar
2011-01-07 16:05                       ` Frederic Weisbecker
2011-01-07 16:13                         ` Jan Beulich
2011-01-07 16:27                           ` Frederic Weisbecker
2011-01-07 16:58                             ` Ingo Molnar
2011-01-07 17:17                               ` Frederic Weisbecker [this message]
2011-01-07 16:33                           ` Frederic Weisbecker
2011-01-07 14:26                     ` Frederic Weisbecker
2011-01-07 12:23 ` [RFC GIT PULL] perf updates Ingo Molnar
2011-01-07 15:24   ` Frederic Weisbecker
2011-01-07 15:37     ` Ingo Molnar

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=20110107171707.GC3066@nowhere \
    --to=fweisbec@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sandmann@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.