public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Naga Chumbalkar <nagananda.chumbalkar@hp.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	oprofile-list@lists.sf.net, tglx@linutronix.de
Subject: Re: [PATCH] x86, perfctr: remove unused func avail_to_resrv_perfctr_nmi()
Date: Mon, 28 Dec 2009 09:38:45 +0100	[thread overview]
Message-ID: <20091228083845.GK28652@elte.hu> (raw)
In-Reply-To: <20091224150458.GA5143@lenovo>


* Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> On Thu, Dec 24, 2009 at 01:54:47AM +0000, Naga Chumbalkar wrote:
> > avail_to_resrv_perfctr_nmi() is neither EXPORT'd, nor used in the file.
> > So remove it.
> > 
> > Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
> > ---
> >  arch/x86/include/asm/nmi.h             |    1 -
> >  arch/x86/kernel/cpu/perfctr-watchdog.c |   11 -----------
> >  2 files changed, 0 insertions(+), 12 deletions(-)
> > 
> 
> Hi Naga, this looks good to me! Thanks.
> 
> Is there any plans to use this routine in future
> so we shouldn't touch this snippet?

Not that i know of.

In fact we should transform/migrate the NMI watchdog driver by making it based 
on a kernel-internal created perf event. (which is what the NMI watchdog 
really is: a periodic NMI event occuring once per second and running a 
callback function.)

That would give us NMI watchdog support on all future x86 CPUs, automatically 
- without having to extend the arch/x86/kernel/cpu/perfctr-watchdog.c code for 
it.

	Ingo

  reply	other threads:[~2009-12-28  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24  1:54 [PATCH] x86, perfctr: remove unused func avail_to_resrv_perfctr_nmi() Naga Chumbalkar
2009-12-24 15:04 ` Cyrill Gorcunov
2009-12-28  8:38   ` Ingo Molnar [this message]
2009-12-28  9:55     ` Cyrill Gorcunov
2009-12-28 10:00       ` Ingo Molnar
2009-12-28 10:07 ` [tip:perf/core] x86, perfctr: Remove " tip-bot for Naga Chumbalkar

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=20091228083845.GK28652@elte.hu \
    --to=mingo@elte.hu \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagananda.chumbalkar@hp.com \
    --cc=oprofile-list@lists.sf.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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