From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Robert Richter <robert.richter@amd.com>,
"David S. Miller" <davem@davemloft.net>,
Jamie Iles <jamie.iles@picochip.com>,
Paul Mundt <lethal@linux-sh.org>,
Arjan van de Ven <arjan@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [RFC][PATCH] perf_events, x86: PEBS support
Date: Tue, 02 Feb 2010 19:33:08 +0100 [thread overview]
Message-ID: <1265135588.24455.350.camel@laptop> (raw)
In-Reply-To: <20100202182653.GB19320@elte.hu>
On Tue, 2010-02-02 at 19:26 +0100, Ingo Molnar wrote:
> * Peter Zijlstra <peterz@infradead.org> wrote:
> > @@ -203,8 +203,9 @@ struct perf_event_attr {
> > enable_on_exec : 1, /* next exec enables */
> > task : 1, /* trace fork/exit */
> > watermark : 1, /* wakeup_watermark */
> > + precise : 1,
>
> I think we want to default to precise events even if not specifically
> requested by user-space, in the cases where that's possible on the CPU
> without additional limitations.
>
> That way people will default to better (and possibly cheaper) PEBS profiling
> on modern Intel CPUs.
Sure, I'll look at that once it starts working :-)
next prev parent reply other threads:[~2010-02-02 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 16:56 [RFC][PATCH] perf_events, x86: PEBS support Peter Zijlstra
2010-02-02 18:26 ` Ingo Molnar
2010-02-02 18:33 ` Peter Zijlstra [this message]
2010-02-03 13:22 ` Stephane Eranian
2010-02-03 13:56 ` Peter Zijlstra
2010-02-03 14:07 ` Stephane Eranian
2010-02-03 14:19 ` Peter Zijlstra
2010-02-03 14:30 ` Stephane Eranian
2010-02-03 14:40 ` Peter Zijlstra
2010-02-03 14:54 ` Stephane Eranian
2010-02-03 15:12 ` Peter Zijlstra
2010-02-03 23:50 ` Peter Zijlstra
2010-02-03 23:51 ` Stephane Eranian
2010-02-04 0:03 ` Peter Zijlstra
2010-02-04 0:22 ` Stephane Eranian
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=1265135588.24455.350.camel@laptop \
--to=peterz@infradead.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jamie.iles@picochip.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=robert.richter@amd.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