public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
	"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>,
	perfmon2-devel@lists.sf.net
Subject: Re: [RFC][PATCH] perf_events, x86: PEBS support
Date: Thu, 04 Feb 2010 00:50:10 +0100	[thread overview]
Message-ID: <1265241010.24455.1627.camel@laptop> (raw)
In-Reply-To: <1265208012.24455.592.camel@laptop>

On Wed, 2010-02-03 at 15:40 +0100, Peter Zijlstra wrote:
> 
> If only they would reset the counter on overflow instead of on record,
> that would solve quite a few issues I imagine. 

So I tried enabling the regular PMC overflow interrupt and reprogramming
the counter from that, but touching the counter seems to destroy the
PEBS assist, so much for that idea.


  parent reply	other threads:[~2010-02-03 23:50 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
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 [this message]
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=1265241010.24455.1627.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=perfmon2-devel@lists.sf.net \
    --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