From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <will.deacon@arm.com>, Ingo Molnar <mingo@kernel.org>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about barriers for ARM on tools/perf/
Date: Fri, 8 May 2015 11:52:55 -0300 [thread overview]
Message-ID: <20150508145255.GK7862@kernel.org> (raw)
In-Reply-To: <20150508143729.GJ7862@kernel.org>
Em Fri, May 08, 2015 at 11:37:29AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, May 08, 2015 at 04:25:13PM +0200, Peter Zijlstra escreveu:
> > He wants to do smp refcounting, which needs atomic_inc() /
> > atomic_inc_non_zero() / atomic_dec_return() etc..
> Right, Will concentrated on what we use those barriers for right now in
> tools/perf.
So, for reference, and this just moves what was already in
tools/perf/perf-sys.h to a place that is named as the kernel is and when
what was used in perf-sys.h is the same as in the kernel, uses the same
kernel source excerpts:
https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=tmp.perf/barrier
- Arnaldo
prev parent reply other threads:[~2015-05-08 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 14:04 Question about barriers for ARM on tools/perf/ Arnaldo Carvalho de Melo
2015-05-08 14:16 ` Peter Zijlstra
2015-05-08 14:21 ` Will Deacon
2015-05-08 14:23 ` Peter Zijlstra
2015-05-08 14:21 ` Will Deacon
2015-05-08 14:25 ` Peter Zijlstra
2015-05-08 14:27 ` Will Deacon
2015-05-08 14:36 ` David Ahern
2015-05-08 14:37 ` Arnaldo Carvalho de Melo
2015-05-08 14:48 ` Will Deacon
2015-05-08 14:57 ` Arnaldo Carvalho de Melo
2015-05-08 15:27 ` Peter Zijlstra
2015-05-08 16:45 ` Will Deacon
2015-05-08 18:18 ` Arnaldo Carvalho de Melo
2015-05-08 14:52 ` Arnaldo Carvalho de Melo [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=20150508145255.GK7862@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.