public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: Re: [V2][PATCH 5/5] oprofile, x86: Reimplement nmi timer mode using perf event
Date: Tue, 1 Nov 2011 18:54:05 +0100	[thread overview]
Message-ID: <20111101175405.GP20173@erda.amd.com> (raw)
In-Reply-To: <20111023112728.GB5156@elte.hu>

On 23.10.11 07:27:28, Ingo Molnar wrote:
> 
> * Robert Richter <robert.richter@amd.com> wrote:
> 
> > The legacy x86 nmi watchdog code was removed with the implementation
> > of the perf based nmi watchdog. This broke Oprofile's nmi timer
> > mode. To run nmi timer mode we relied on a continuous ticking nmi
> > source which the nmi watchdog provided. The nmi tick was no longer
> > available and current watchdog can not be used anymore since it runs
> > with very long periods in the range of seconds. This patch
> > reimplements the nmi timer mode using a perf counter nmi source.
> > 
> > V2:
> > * removing pr_info()
> > * fix undefined reference to `__udivdi3' for 32 bit build
> > * fix section mismatch of .cpuinit.data:nmi_timer_cpu_nb
> > * removed nmi timer setup in arch/x86
> > * implemented function stubs for op_nmi_init/exit()
> > * made code more readable in oprofile_init()
> > 
> > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Signed-off-by: Robert Richter <robert.richter@amd.com>
> > ---
> >  arch/Kconfig                      |    4 +
> >  arch/x86/oprofile/Makefile        |    3 +-
> >  arch/x86/oprofile/init.c          |   30 ++-----
> >  arch/x86/oprofile/nmi_timer_int.c |   66 --------------
> >  drivers/oprofile/nmi_timer_int.c  |  173 +++++++++++++++++++++++++++++++++++++
> >  drivers/oprofile/oprof.c          |   24 +++---
> >  drivers/oprofile/oprof.h          |    9 ++
> >  kernel/events/core.c              |    2 +
> >  8 files changed, 208 insertions(+), 103 deletions(-)
> >  delete mode 100644 arch/x86/oprofile/nmi_timer_int.c
> >  create mode 100644 drivers/oprofile/nmi_timer_int.c
> 
> Looks clean to me. Peter, any objections?

Peter, I guess V2 is ok for you too?

Thanks,

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 18:47 [V2][PATCH 0/5] oprofile: Updates and fixes for timer modes Robert Richter
2011-10-19 18:47 ` [V2][PATCH 1/5] oprofile, x86: Add kernel parameter oprofile.cpu_type=timer Robert Richter
2011-10-19 18:47 ` [V2][PATCH 2/5] oprofile: Fix crash when unloading module (hr timer mode) Robert Richter
2011-10-19 18:47 ` [V2][PATCH 3/5] oprofile, x86: Fix crash when unloading module (nmi " Robert Richter
2011-10-19 18:47 ` [V2][PATCH 4/5] oprofile: Remove exit function for timer mode Robert Richter
2011-10-19 18:47 ` [V2][PATCH 5/5] oprofile, x86: Reimplement nmi timer mode using perf event Robert Richter
2011-10-23 11:27   ` Ingo Molnar
2011-11-01 17:54     ` Robert Richter [this message]
2011-11-10 12:52     ` Peter Zijlstra

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=20111101175405.GP20173@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=peterz@infradead.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