public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Soeren Sandmann Pedersen <sandmann@redhat.com>
Subject: Re: [RFC GIT PULL] perf updates
Date: Fri, 7 Jan 2011 16:24:29 +0100	[thread overview]
Message-ID: <20110107152421.GA2631@nowhere> (raw)
In-Reply-To: <20110107122317.GA20761@elte.hu>

On Fri, Jan 07, 2011 at 01:23:17PM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > Ingo,
> > 
> > Please pull the perf/core branch that can be found at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > 	perf/core
> > 	
> > Soeren reported some time ago that callchains were broken on
> > x86_64 with cpu-clock/task-clock events. After some time I
> > finally found the problem was in the irq low level arg saving.
> > It touches fragile code though, I hope some people can
> > have a look over the fix.
> > 
> > Thanks,
> > 	Frederic
> > ---
> > 
> > Frederic Weisbecker (2):
> >       x86: Fix rbp saving in pt_regs on irq entry
> >       perf: Build tools with frame pointer
> 
> Is this variant fine with Jan too?

So, Arnaldo has picked up the second patch.

For the first I need to resend with a fix on CFI annotations.

  reply	other threads:[~2011-01-07 15:24 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
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 [this message]
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=20110107152421.GA2631@nowhere \
    --to=fweisbec@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sandmann@redhat.com \
    /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