From: Eric B Munson <emunson@mgebm.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
paulus@samba.org, anton@samba.org, acme@ghostprotocols.net,
mingo@elte.hu, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] POWER: perf_event: Skip updating kernel counters if register value shrinks
Date: Thu, 7 Apr 2011 12:16:11 -0400 [thread overview]
Message-ID: <20110407161611.GC3119@mgebm.net> (raw)
In-Reply-To: <1302150177.2458.30.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Thu, 07 Apr 2011, Benjamin Herrenschmidt wrote:
>
> > > Doesn't that mean that power_pmu_read() can only ever increase the value of
> > > the perf_event and so will essentially -stop- once the counter rolls over ?
> > >
> > > Similar comments every where you do this type of comparison.
> > >
> > > Cheers,
> > > Ben.
> >
> > Sorry for the nag, but am I missing something about the way the register and
> > the previous values are reset in the overflow interrupt handler?
>
> Well, not all counters get interrupts right ? Some counters are just
> free running... I'm not sure when that power_pmu_read() function is
> actually used by the core, I'm not that familiar with perf, but I'd say
> better safe than sorry. When comparing counter values, doing in a way
> that is generally safe vs. wraparounds. Eventually do a helper for that.
>
> Cheers,
> Ben.
I am honestly not sure, I was under the assumption that all counters would
generate an interrupt if they overflowed. I do not have the hardware docs to
prove this, so I will have a V3 that (I think/hope) addresses your concerns out
momentarily.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric B Munson <emunson@mgebm.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@elte.hu,
acme@ghostprotocols.net, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, anton@samba.org
Subject: Re: [PATCH] POWER: perf_event: Skip updating kernel counters if register value shrinks
Date: Thu, 7 Apr 2011 12:16:11 -0400 [thread overview]
Message-ID: <20110407161611.GC3119@mgebm.net> (raw)
In-Reply-To: <1302150177.2458.30.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Thu, 07 Apr 2011, Benjamin Herrenschmidt wrote:
>
> > > Doesn't that mean that power_pmu_read() can only ever increase the value of
> > > the perf_event and so will essentially -stop- once the counter rolls over ?
> > >
> > > Similar comments every where you do this type of comparison.
> > >
> > > Cheers,
> > > Ben.
> >
> > Sorry for the nag, but am I missing something about the way the register and
> > the previous values are reset in the overflow interrupt handler?
>
> Well, not all counters get interrupts right ? Some counters are just
> free running... I'm not sure when that power_pmu_read() function is
> actually used by the core, I'm not that familiar with perf, but I'd say
> better safe than sorry. When comparing counter values, doing in a way
> that is generally safe vs. wraparounds. Eventually do a helper for that.
>
> Cheers,
> Ben.
I am honestly not sure, I was under the assumption that all counters would
generate an interrupt if they overflowed. I do not have the hardware docs to
prove this, so I will have a V3 that (I think/hope) addresses your concerns out
momentarily.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-04-07 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 13:28 [PATCH] POWER: perf_event: Skip updating kernel counters if register value shrinks Eric B Munson
2011-03-25 13:28 ` Eric B Munson
2011-03-29 6:03 ` Benjamin Herrenschmidt
2011-03-29 6:03 ` Benjamin Herrenschmidt
2011-03-29 14:25 ` Eric B Munson
2011-03-29 14:25 ` Eric B Munson
2011-03-29 21:12 ` Benjamin Herrenschmidt
2011-03-29 21:12 ` Benjamin Herrenschmidt
2011-03-30 18:36 ` Eric B Munson
2011-03-30 18:36 ` Eric B Munson
2011-03-31 6:04 ` Benjamin Herrenschmidt
2011-03-31 6:04 ` Benjamin Herrenschmidt
2011-03-31 16:14 ` Eric B Munson
2011-03-31 16:14 ` Eric B Munson
2011-04-06 21:27 ` Eric B Munson
2011-04-06 21:27 ` Eric B Munson
2011-04-07 4:22 ` Benjamin Herrenschmidt
2011-04-07 4:22 ` Benjamin Herrenschmidt
2011-04-07 16:16 ` Eric B Munson [this message]
2011-04-07 16:16 ` Eric B Munson
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=20110407161611.GC3119@mgebm.net \
--to=emunson@mgebm.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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.