From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf: do not set task_ctx pointer in cpuctx if there is no events in the context
Date: Mon, 14 Nov 2011 11:50:54 +0100 [thread overview]
Message-ID: <1321267854.1421.4.camel@twins> (raw)
In-Reply-To: <20111113160605.GW3225@redhat.com>
On Sun, 2011-11-13 at 18:06 +0200, Gleb Natapov wrote:
> On Mon, Nov 07, 2011 at 02:00:11PM +0100, Peter Zijlstra wrote:
> > On Thu, 2011-11-03 at 09:41 +0200, Gleb Natapov wrote:
> > > Ingo, Peter can you look into this please.
> >
> > queued it and the jump_label thing.
> I see jump_label thing in tip/perf/core but not this one yet. This is
> good because this one needs amendment :) See below.
Weird ass stuff, because my copy still applies to tip/master. Ingo, wtf
is up?
> ---
>
> Do not set task_ctx pointer during sched_in if there is no
> events associated with the context. Otherwise if during task
> execution total number of events in the system will become zero
> perf_event_context_sched_out() will not be called and cpuctx->task_ctx
> will be left with a stale value. Also perf_event_sched_in() shouldn't try
> to schedule task events in this case otherwise cpuctx->task_ctx->is_active
> will not be cleared during sched_out and will become incorrect.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
--- missing right there
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index d1a1bee..7210657 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -2171,9 +2171,10 @@ static void perf_event_context_sched_in(struct perf_event_context *ctx,
> */
> cpu_ctx_sched_out(cpuctx, EVENT_FLEXIBLE);
>
> - perf_event_sched_in(cpuctx, ctx, task);
> + if (ctx->nr_events)
> + cpuctx->task_ctx = ctx;
>
> - cpuctx->task_ctx = ctx;
> + perf_event_sched_in(cpuctx, cpuctx->task_ctx, task);
>
> perf_pmu_enable(ctx->pmu);
> perf_ctx_unlock(cpuctx, ctx);
> --
> Gleb.
next prev parent reply other threads:[~2011-11-14 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 17:10 [PATCH] perf: do not set task_ctx pointer in cpuctx if there is no events in the context Gleb Natapov
2011-11-03 7:41 ` Gleb Natapov
2011-11-07 13:00 ` Peter Zijlstra
2011-11-13 16:06 ` Gleb Natapov
2011-11-14 10:50 ` Peter Zijlstra [this message]
2011-11-18 23:32 ` [tip:perf/urgent] perf: Do not set task_ctx pointer in cpuctx if there are " tip-bot for Gleb Natapov
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=1321267854.1421.4.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox