mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: paulus@samba.org, mingo@elte.hu, linux-kernel@vger.kernel.org,
	oleg@redhat.com
Subject: Re: [PATCH] perf, core: Fix initial task_ctx/event installation
Date: Tue, 7 Jun 2011 00:28:56 +0200	[thread overview]
Message-ID: <20110606222856.GA2280@jolsa.Belkin> (raw)
In-Reply-To: <1307399008.2497.971.camel@laptop>

On Tue, Jun 07, 2011 at 12:23:28AM +0200, Peter Zijlstra wrote:
> This works for me..
> 
> ---
>  kernel/events/core.c |   28 +++++++++++++++++-----------
>  1 files changed, 17 insertions(+), 11 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index ba89f40..5e8c7b1 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -1505,25 +1505,31 @@ static int  __perf_install_in_context(void *info)
>  	struct perf_event_context *task_ctx = cpuctx->task_ctx;
>  	struct task_struct *task = current;
>  
> -	perf_ctx_lock(cpuctx, cpuctx->task_ctx);
> +	perf_ctx_lock(cpuctx, task_ctx);
>  	perf_pmu_disable(cpuctx->ctx.pmu);
>  
>  	/*
>  	 * If there was an active task_ctx schedule it out.
>  	 */
> -	if (task_ctx) {
> +	if (task_ctx)
>  		task_ctx_sched_out(task_ctx);
> -		/*
> -		 * If the context we're installing events in is not the
> -		 * active task_ctx, flip them.
> -		 */
> -		if (ctx->task && task_ctx != ctx) {
> -			raw_spin_unlock(&cpuctx->ctx.lock);
> -			raw_spin_lock(&ctx->lock);
> -			cpuctx->task_ctx = task_ctx = ctx;
> -		}
> +
> +	/*
> +	 * If the context we're installing events in is not the
> +	 * active task_ctx, flip them.
> +	 */
> +	if (ctx->task && task_ctx != ctx) {
> +		if (task_ctx)
> +			raw_spin_unlock(&task_ctx->lock);
> +		raw_spin_lock(&ctx->lock);
> +		task_ctx = ctx;
> +	}
> +
> +	if (task_ctx) {
> +		cpuctx->task_ctx = task_ctx;
>  		task = task_ctx->task;
>  	}
> +
>  	cpu_ctx_sched_out(cpuctx, EVENT_ALL);
>  
>  	update_context_time(ctx);
> 
> 

just came back :) seems ok.. I'll test tomorow and let you know

thanks,
jirka

  reply	other threads:[~2011-06-06 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 14:38 Jiri Olsa
2011-06-06 17:40 ` Peter Zijlstra
2011-06-06 18:27   ` Peter Zijlstra
2011-06-06 22:23     ` Peter Zijlstra
2011-06-06 22:28       ` Jiri Olsa [this message]
2011-06-07 12:10         ` Jiri Olsa
2011-06-07 12:03       ` [tip:perf/core] " 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=20110606222856.GA2280@jolsa.Belkin \
    --to=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®