All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince Weaver <vweaver1@eecs.utk.edu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: <mingo@redhat.com>, <hpa@zytor.com>, <eranian@google.com>,
	<linux-kernel@vger.kernel.org>, <tglx@linutronix.de>,
	<mingo@elte.hu>
Subject: Re: [tip:perf/urgent] perf/x86: Enable raw event access to Intel offcore events
Date: Mon, 21 Nov 2011 14:01:51 -0500	[thread overview]
Message-ID: <alpine.DEB.2.00.1111211358570.23676@cl320.eecs.utk.edu> (raw)
In-Reply-To: <1321901536.28118.20.camel@twins>

On Mon, 21 Nov 2011, Peter Zijlstra wrote:
> On Mon, 2011-11-21 at 13:24 -0500, Vince Weaver wrote:

> > Now I'll have to find something else 
> > to complain about, probably the scedulability issue introduced with the
> > NMI watchdog.
> 
> But you can disable that thing, right?
> 
> echo 0 > /proc/sys/kernel/nmi_watchdog;
> 
> or so should do the trick.

yes, if the user running PAPI has root.

That's unfortunately not always the case, and sometimes people want to 
have both the NMI watchdog operating and use PAPI simultaneously.

We have a workaround, but it currently disables kernel multiplexing and a 
few other nice features.

Vince
vweaver1@eecs.utk.edu


  reply	other threads:[~2011-11-21 19:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 16:05 [perf] enable raw OFFCORE_EVENTS for non-perf userspace Vince Weaver
2011-08-03 17:00 ` Vince Weaver
2011-08-04 15:55 ` Peter Zijlstra
2011-08-05  2:24   ` Vince Weaver
2011-08-05  9:49   ` Ingo Molnar
2011-11-07 18:30   ` Vince Weaver
2011-11-18 23:34 ` [tip:perf/urgent] perf/x86: Enable raw event access to Intel offcore events tip-bot for Peter Zijlstra
2011-11-21 18:24   ` Vince Weaver
2011-11-21 18:52     ` Peter Zijlstra
2011-11-21 19:01       ` Vince Weaver [this message]
2011-11-21 19:04         ` Stephane Eranian
2011-11-21 21:04           ` Vince Weaver
2011-11-21 21:39             ` Stephane Eranian
2011-11-21 21:42               ` Peter Zijlstra
2011-11-21 21:45                 ` Stephane Eranian
2011-11-21 21:48                   ` Peter Zijlstra
2011-11-21 22:05             ` 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=alpine.DEB.2.00.1111211358570.23676@cl320.eecs.utk.edu \
    --to=vweaver1@eecs.utk.edu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=eranian@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.