public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Will Deacon <will.deacon@arm.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
	"dengcheng.zhu@gmail.com" <dengcheng.zhu@gmail.com>,
	"fweisbec@gmail.com" <fweisbec@gmail.com>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"dzickus@redhat.com" <dzickus@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"anton@samba.org" <anton@samba.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
	"lethal@linux-sh.org" <lethal@linux-sh.org>,
	"emunson@mgebm.net" <emunson@mgebm.net>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"mcree@orcon.net.nz" <mcree@orcon.net.nz>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:perf/core] perf: Remove the nmi parameter from the swevent and overflow interface
Date: Fri, 08 Jul 2011 19:41:16 +0200	[thread overview]
Message-ID: <1310146876.3282.711.camel@twins> (raw)
In-Reply-To: <20110708173442.GB31972@e102144-lin.cambridge.arm.com>

On Fri, 2011-07-08 at 18:34 +0100, Will Deacon wrote:
> Hi Peter,
> 
> On Fri, Jul 01, 2011 at 04:21:25PM +0100, tip-bot for Peter Zijlstra wrote:
> > Commit-ID:  a8b0ca17b80e92faab46ee7179ba9e99ccb61233
> > Gitweb:     http://git.kernel.org/tip/a8b0ca17b80e92faab46ee7179ba9e99ccb61233
> > Author:     Peter Zijlstra <a.p.zijlstra@chello.nl>
> > AuthorDate: Mon, 27 Jun 2011 14:41:57 +0200
> > Committer:  Ingo Molnar <mingo@elte.hu>
> > CommitDate: Fri, 1 Jul 2011 11:06:35 +0200
> > 
> > perf: Remove the nmi parameter from the swevent and overflow interface
> > 
> > The nmi parameter indicated if we could do wakeups from the current
> > context, if not, we would set some state and self-IPI and let the
> > resulting interrupt do the wakeup.
> > 
> > For the various event classes:
> > 
> >   - hardware: nmi=0; PMI is in fact an NMI or we run irq_work_run from
> >     the PMI-tail (ARM etc.)
> >   - tracepoint: nmi=0; since tracepoint could be from NMI context.
> >   - software: nmi=[0,1]; some, like the schedule thing cannot
> >     perform wakeups, and hence need 0.
> > 
> > As one can see, there is very little nmi=1 usage, and the down-side of
> > not using it is that on some platforms some software events can have a
> > jiffy delay in wakeup (when arch_irq_work_raise isn't implemented).
> > 
> > The up-side however is that we can remove the nmi parameter and save a
> > bunch of conditionals in fast paths.
> > 
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> 
> Whilst you updated the arch code in this series, you forgot to update the
> oprofile perf backend. 

Bah, I bet it skillfully hid from my grep-foo.

> I think you want something as simple as:
> 
> 
> diff --git a/drivers/oprofile/oprofile_perf.c b/drivers/oprofile/oprofile_perf.c
> index 59acf9e..94796f3 100644
> --- a/drivers/oprofile/oprofile_perf.c
> +++ b/drivers/oprofile/oprofile_perf.c
> @@ -31,7 +31,7 @@ static int num_counters;
>  /*
>   * Overflow callback for oprofile.
>   */
> -static void op_overflow_handler(struct perf_event *event, int unused,
> +static void op_overflow_handler(struct perf_event *event,
>                         struct perf_sample_data *data, struct pt_regs *regs)
>  {
>         int id;
> 

Yes, that is sufficient. Thanks!

  reply	other threads:[~2011-07-08 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 15:21 [tip:perf/core] perf: Remove the nmi parameter from the swevent and overflow interface tip-bot for Peter Zijlstra
2011-07-08 17:34 ` Will Deacon
2011-07-08 17:41   ` Peter Zijlstra [this message]
2011-07-21 14:10     ` Will Deacon
2011-07-21 14:13       ` Peter Zijlstra
2011-07-21 19:32   ` [tip:perf/core] perf: Remove the nmi parameter from the oprofile_perf backend tip-bot for Will Deacon

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=1310146876.3282.711.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=dengcheng.zhu@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=emunson@mgebm.net \
    --cc=fweisbec@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=jason.wessel@windriver.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.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