public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jason Baron <jbaron@redhat.com>
Cc: eranian@googlemail.com, linux-kernel@vger.kernel.org,
	mingo@elte.hu, paulus@samba.org, perfmon2-devel@lists.sf.net
Subject: Re: [PATCH] perf: fix cmpxchg warning in perf_event_amd.c
Date: Wed, 19 May 2010 08:32:56 +0200	[thread overview]
Message-ID: <1274250776.5605.10000.camel@twins> (raw)
In-Reply-To: <20100518204330.GA30624@redhat.com>

On Tue, 2010-05-18 at 16:43 -0400, Jason Baron wrote:
> Hi,
> 
> I'm getting the following warnings:
> 
> In file included from arch/x86/kernel/cpu/perf_event.c:1343:
> arch/x86/kernel/cpu/perf_event_amd.c: In function
> ‘amd_put_event_constraints’:
> arch/x86/kernel/cpu/perf_event_amd.c:167: warning: value computed is not
> used
> 
> Since cmpxchg returns a value, we need to use it. We can use it to test if its
> equal to "event".

Should we:

 a) add a WARN_ONCE() there and make use of the return value (it should
never happen)

or

 b) replace the lot with: nb->owners[i] = NULL; which should I _think_
work.

> Signed-off-by: Jason Baron <jbaron@redhat.com>
> ---
>  arch/x86/kernel/cpu/perf_event_amd.c |    4 +---
>  1 files changed, 1 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/perf_event_amd.c b/arch/x86/kernel/cpu/perf_event_amd.c
> index 611df11..e13ce4a 100644
> --- a/arch/x86/kernel/cpu/perf_event_amd.c
> +++ b/arch/x86/kernel/cpu/perf_event_amd.c
> @@ -163,10 +163,8 @@ static void amd_put_event_constraints(struct cpu_hw_events *cpuc,
>  	 * when we come here
>  	 */
>  	for (i = 0; i < x86_pmu.num_counters; i++) {
> -		if (nb->owners[i] == event) {
> -			cmpxchg(nb->owners+i, event, NULL);
> +		if (cmpxchg(nb->owners+i, event, NULL) == event)
>  			break;
> -		}
>  	}
>  }
>  


      reply	other threads:[~2010-05-19  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 20:43 [PATCH] perf: fix cmpxchg warning in perf_event_amd.c Jason Baron
2010-05-19  6:32 ` Peter Zijlstra [this message]

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=1274250776.5605.10000.camel@twins \
    --to=peterz@infradead.org \
    --cc=eranian@googlemail.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=perfmon2-devel@lists.sf.net \
    /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