From: Arun Sharma <asharma@fb.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>,
<linux-kernel@vger.kernel.org>, <mingo@elte.hu>,
<gleb@redhat.com>, <wcohen@redhat.com>, <vince@deater.net>,
<andi@firstfloor.org>
Subject: Re: [PATCH] perf_events: fix broken intr throttling (v3)
Date: Thu, 26 Jan 2012 10:22:28 -0800 [thread overview]
Message-ID: <4F2199E4.3020107@fb.com> (raw)
In-Reply-To: <1327594589.2446.112.camel@twins>
On 1/26/12 8:16 AM, Peter Zijlstra wrote:
> On Thu, 2012-01-26 at 17:03 +0100, Stephane Eranian wrote:
>> This patch fixes the throttling mechanism. It was broken
>> in 3.2.0. Events were not being unthrottled. The unthrottling
>> mechanism required that events be checked at each timer tick.
>>
>> This patch solves this problem and also separates:
>> - unthrottling
>> - multiplexing
>> - frequency-mode period adjustments
>
> Thanks!
Should this be Cc'ed to stable@?
-Arun
next prev parent reply other threads:[~2012-01-26 18:23 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 [this message]
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
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=4F2199E4.3020107@fb.com \
--to=asharma@fb.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.