From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
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 12:07:49 +0100 [thread overview]
Message-ID: <20151117110749.GT3816@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075F44D210D@IN01WEMBXA.internal.synopsys.com>
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.
next prev parent reply other threads:[~2015-11-17 11:07 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 [this message]
2015-11-17 11:23 ` Vineet Gupta
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=20151117110749.GT3816@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.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