From: Will Deacon <will.deacon@arm.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH 1/2] perf: fix PERF_EVENT_IOC_PERIOD to force-reset the period
Date: Thu, 12 Dec 2013 18:27:47 +0000 [thread overview]
Message-ID: <20131212182747.GL12617@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1385560479-11014-1-git-send-email-will.deacon@arm.com>
Hi Peter,
Do you have any thoughts on the below? It would be good to add your
signed-off to the patch, since you wrote it originally.
Cheers,
Will
On Wed, Nov 27, 2013 at 01:54:38PM +0000, Will Deacon wrote:
> From: Peter Zijlstra <peterz@infradead.org>
>
> Vince Weaver reports that, on all architectures apart from ARM,
> PERF_EVENT_IOC_PERIOD doesn't actually update the period until the next
> event fires. This is counter-intuitive behaviour and is better dealt
> with in the core code.
>
> This patch ensures that the period is forcefully reset when dealing with
> such a request in the core code. A subsequent patch removes the
> equivalent hack from the ARM back-end.
>
> Cc: Vince Weaver <vincent.weaver@maine.edu>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
>
> Peter -- I didn't want this to get lost, so I picked it up, fixed a typo
> and wrote a commit message. Could I add your SoB please?
>
> Cheers,
> Will
>
> kernel/events/core.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index d724e7757cd1..1c626b923ddf 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -3527,7 +3527,7 @@ static void perf_event_for_each(struct perf_event *event,
> static int perf_event_period(struct perf_event *event, u64 __user *arg)
> {
> struct perf_event_context *ctx = event->ctx;
> - int ret = 0;
> + int ret = 0, active;
> u64 value;
>
> if (!is_sampling_event(event))
> @@ -3551,6 +3551,20 @@ static int perf_event_period(struct perf_event *event, u64 __user *arg)
> event->attr.sample_period = value;
> event->hw.sample_period = value;
> }
> +
> + active = (event->state == PERF_EVENT_STATE_ACTIVE);
> + if (active) {
> + perf_pmu_disable(ctx->pmu);
> + event->pmu->stop(event, PERF_EF_UPDATE);
> + }
> +
> + local64_set(&event->hw.period_left, 0);
> +
> + if (active) {
> + event->pmu->start(event, PERF_EF_RELOAD);
> + perf_pmu_enable(ctx->pmu);
> + }
> +
> unlock:
> raw_spin_unlock_irq(&ctx->lock);
>
> --
> 1.8.2.2
>
next prev parent reply other threads:[~2013-12-12 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 13:54 Will Deacon
2013-11-27 13:54 ` [PATCH 2/2] Revert "ARM: 7556/1: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD" Will Deacon
2013-12-18 10:32 ` [tip:perf/core] " tip-bot for Will Deacon
2013-11-27 15:15 ` [PATCH 1/2] perf: fix PERF_EVENT_IOC_PERIOD to force-reset the period Vince Weaver
2013-12-12 18:27 ` Will Deacon [this message]
2013-12-13 15:13 ` Peter Zijlstra
2013-12-18 10:32 ` [tip:perf/core] perf: Fix " tip-bot for Peter Zijlstra
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=20131212182747.GL12617@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®