From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vince Weaver <vweaver1@eecs.utk.edu>
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 19:52:16 +0100 [thread overview]
Message-ID: <1321901536.28118.20.camel@twins> (raw)
In-Reply-To: <alpine.DEB.2.00.1111211321390.21667@cl320.eecs.utk.edu>
On Mon, 2011-11-21 at 13:24 -0500, Vince Weaver wrote:
> On Fri, 18 Nov 2011, tip-bot for Peter Zijlstra wrote:
>
> > Commit-ID: ed13ec58bfe0d5dc95f748e6118432cb0fa283cb
> > Gitweb: http://git.kernel.org/tip/ed13ec58bfe0d5dc95f748e6118432cb0fa283cb
> > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > AuthorDate: Mon, 14 Nov 2011 10:03:25 +0100
> > Committer: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Mon, 14 Nov 2011 13:03:44 +0100
> >
> > perf/x86: Enable raw event access to Intel offcore events
>
> awesome. You can add a "Whined-about-it-at-great-length: Vince Weaver"
> line to the commit logs if you want. 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.
next prev parent reply other threads:[~2011-11-21 18:52 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 [this message]
2011-11-21 19:01 ` Vince Weaver
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=1321901536.28118.20.camel@twins \
--to=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 \
--cc=vweaver1@eecs.utk.edu \
/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