public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	arcml <linux-snps-arc@lists.infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: local64_cmpxchg() in arc_perf_event_update()
Date: Tue, 17 Nov 2015 16:53:04 +0530	[thread overview]
Message-ID: <564B0E18.3040207@synopsys.com> (raw)
In-Reply-To: <20151117110749.GT3816@twins.programming.kicks-ass.net>

On Tuesday 17 November 2015 04:37 PM, Peter Zijlstra wrote:
> On Tue, Nov 17, 2015 at 09:14:59AM +0000, Vineet Gupta wrote:
>> > Let's check with Peter as I'm not sure how exactly the read call will
>> > nest for same counter on same core ?
> Various possible ways, but the easiest is userspace doing a sys_read()
> on the counter while the NMI happens.
> 
> 

That means Alexey need to revert the hunk ?

 static void arc_perf_event_update(struct perf_event *event,
 				  struct hw_perf_event *hwc, int idx)
 {
-	uint64_t prev_raw_count, new_raw_count;
-	int64_t delta;
-
-	do {
-		prev_raw_count = local64_read(&hwc->prev_count);
-		new_raw_count = arc_pmu_read_counter(idx);
-	} while (local64_cmpxchg(&hwc->prev_count, prev_raw_count,
-				 new_raw_count) != prev_raw_count);
-
-	delta = (new_raw_count - prev_raw_count) &
-		((1ULL << arc_pmu->counter_size) - 1ULL);
+	uint64_t prev_raw_count = local64_read(&hwc->prev_count);
+	uint64_t new_raw_count = arc_pmu_read_counter(idx);
+	int64_t delta = new_raw_count - prev_raw_count;

+	/*
+	 * We don't afaraid of hwc->prev_count changing beneath our feet
+	 * because there's no way for us to re-enter this function anytime.
+	 */
+	local64_set(&hwc->prev_count, new_raw_count);

  reply	other threads:[~2015-11-17 11:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1445286926.3913.13.camel@synopsys.com>
2015-11-17  9:14 ` local64_cmpxchg() in arc_perf_event_update() Vineet Gupta
2015-11-17 11:07   ` Peter Zijlstra
2015-11-17 11:23     ` Vineet Gupta [this message]
2015-11-17 12:24       ` Peter Zijlstra
2015-11-17 12:25         ` Peter Zijlstra
2015-11-17 12:53           ` NMI for ARC Vineet Gupta
2015-11-17 13:15             ` Peter Zijlstra
2016-09-28  0:22               ` Vineet Gupta
2016-09-28  7:16                 ` Peter Zijlstra
2016-09-28 17:58                   ` Vineet Gupta
2016-09-28 19:25                   ` Andy Lutomirski
2016-09-28 20:37                     ` Peter Zijlstra
2016-09-28 22:26                       ` Andy Lutomirski
2016-09-28 22:44                         ` Vineet Gupta
2016-09-28 22:47                           ` Andy Lutomirski
2016-09-29  1:20                         ` Vineet Gupta
2016-09-29  6:43                           ` Peter Zijlstra
2016-09-29 16:47                             ` Vineet Gupta
2016-09-29 18:54                               ` Andy Lutomirski
2016-09-29 19:48                                 ` Vineet Gupta
2016-09-30 10:49                                   ` Peter Zijlstra
2016-09-29 17:30                           ` Andy Lutomirski
2015-11-17 13:24           ` local64_cmpxchg() in arc_perf_event_update() Vineet Gupta

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=564B0E18.3040207@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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