From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "H. Peter Anvin" <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
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>
Subject: Re: [RFC PATCH 1/2] x86: Fix rbp saving in pt_regs on irq entry
Date: Fri, 7 Jan 2011 17:33:50 +0100 [thread overview]
Message-ID: <20110107163347.GB3066@nowhere> (raw)
In-Reply-To: <4D2749D6020000780002B0BC@vpn.id2.novell.com>
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?
Actually I couldn't test kernel CFI annotations with perf as we
keep the kernel unwinding under frame pointer style.
The CFI unwinding we'll do is only for userspace.
next prev parent reply other threads:[~2011-01-07 16:33 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
2011-01-07 16:33 ` Frederic Weisbecker [this message]
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=20110107163347.GB3066@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 \
/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