All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Stephane Eranian <eranian@google.com>,
	Anton Blanchard <anton@samba.org>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@elte.hu, gleb@redhat.com, wcohen@redhat.com,
	vince@deater.net, asharma@fb.com, andi@firstfloor.org,
	paulus@samba.org, emunson@mgebm.net, imunsie@au1.ibm.com,
	Matt Helsley <matthltc@us.ibm.com>
Subject: Re: [PATCH] perf_events: fix broken intr throttling (v3)
Date: Tue, 14 Feb 2012 18:37:05 -0800	[thread overview]
Message-ID: <20120215023705.GA13042@us.ibm.com> (raw)
In-Reply-To: <1328854519.3019.3.camel@pasglop>

Benjamin Herrenschmidt [benh@kernel.crashing.org] wrote:
| On Thu, 2012-02-09 at 19:19 -0800, Sukadev Bhattiprolu wrote:
| > Stephane Eranian [eranian@google.com] wrote:
| > | On Wed, Feb 8, 2012 at 12:32 PM, Anton Blanchard <anton@samba.org> wrote:
| > | >
| > | > Hi,
| > | >
| > | > On Thu, 26 Jan 2012 17:03:19 +0100
| The powerpc .git tree is not useful at this point, I haven't opened
| powerpc -next yet so it's just all old stale stuff. Please work with
| upstream always unless you have a very good reason to use my tree. It's
| really only meant as a conduit between me and Linus or for -next.

Ok.

I tried this on current mainline (commit 13d261932) which now includes both
of Stephane's patches and repeated the nooploop test.

The problem still exists - the number of events reported on Power is far
fewer than without the patches.

Aggregated stats:
           TOTAL events:         78
            MMAP events:         47
            COMM events:          2
            EXIT events:          2
          SAMPLE events:         27
cycles stats:
           TOTAL events:         21
            MMAP events:          4
            COMM events:          1
            EXIT events:          2
          SAMPLE events:         14
cycles stats:
           TOTAL events:         13
          SAMPLE events:         13

Sukadev


  reply	other threads:[~2012-02-15  2:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 16:03 [PATCH] perf_events: fix broken intr throttling (v3) Stephane Eranian
2012-01-26 16:16 ` Peter Zijlstra
2012-01-26 18:22   ` Arun Sharma
2012-01-28 12:04 ` [tip:perf/urgent] perf: Fix broken interrupt rate throttling tip-bot for Stephane Eranian
2012-02-08 11:32 ` [PATCH] perf_events: fix broken intr throttling (v3) Anton Blanchard
2012-02-08 11:43   ` Stephane Eranian
2012-02-10  3:19     ` Sukadev Bhattiprolu
2012-02-10  6:15       ` Benjamin Herrenschmidt
2012-02-15  2:37         ` Sukadev Bhattiprolu [this message]
2012-02-19 11:26           ` Stephane Eranian
2012-02-20 19:01             ` Sukadev Bhattiprolu
2012-02-09  5:23 ` Anshuman Khandual
2012-02-09 22:45   ` 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=20120215023705.GA13042@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=anton@samba.org \
    --cc=asharma@fb.com \
    --cc=benh@kernel.crashing.org \
    --cc=emunson@mgebm.net \
    --cc=eranian@google.com \
    --cc=gleb@redhat.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=vince@deater.net \
    --cc=wcohen@redhat.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 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.