All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Robert Richter <robert.richter@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"oprofile-list@lists.sourceforge.net" 
	<oprofile-list@lists.sourceforge.net>
Subject: Re: [GIT PULL] oprofile fixes for v3.0
Date: Tue, 21 Jun 2011 15:03:08 +0200	[thread overview]
Message-ID: <20110621130308.GA22088@elte.hu> (raw)
In-Reply-To: <20110621125219.GZ20052@erda.amd.com>


Robert,

* Robert Richter <robert.richter@amd.com> wrote:

> Ingo,
> 
> please pull oprofile fixes for v3.0 (tip/perf/urgent):
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
> 
> Thanks,
> 
> -Robert
> 
> 
> The following changes since commit 2c53b436a30867eb6b47dd7bab23ba638d1fb0d2:
> 
>   Linux 3.0-rc3 (2011-06-13 15:29:59 -0700)
> 
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
> 
> Robert Richter (2):
>       oprofile, x86: Fix race in nmi handler while starting counters
>       oprofile, x86: Fix nmi-unsafe callgraph support
> 
>  arch/x86/oprofile/backtrace.c |   56 ++++++++++++++++++++++++++++++++++------
>  arch/x86/oprofile/nmi_int.c   |   14 +++++++---
>  2 files changed, 57 insertions(+), 13 deletions(-)

Since when has NMI callgraph support been broken?

Thanks,

	Ingo

  reply	other threads:[~2011-06-21 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 12:52 [GIT PULL] oprofile fixes for v3.0 Robert Richter
2011-06-21 13:03 ` Ingo Molnar [this message]
2011-06-21 17:54   ` Robert Richter
2011-06-21 20:18     ` Ingo Molnar
2011-06-22 13:50       ` Robert Richter
  -- strict thread matches above, loose matches on Subject: below --
2011-05-31 16:46 [PATCH 0/3] oprofile fixes for 3.0 Robert Richter
2011-06-08 12:53 ` [GIT PULL] oprofile fixes for v3.0 Robert Richter
2011-06-08 14:06   ` Ingo Molnar
2011-06-09  7:02     ` Robert Richter
2011-06-09  7:15       ` 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=20110621130308.GA22088@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=robert.richter@amd.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 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.