From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Jamie Iles <jamie.iles@picochip.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 1/2] perf tools: allow building for ARM
Date: Fri, 11 Dec 2009 21:22:22 +0000 [thread overview]
Message-ID: <20091211212222.GD12628@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <19234.11393.632298.555005@pilspetsen.it.uu.se>
On Fri, Dec 11, 2009 at 12:26:57PM +0100, Mikael Pettersson wrote:
> The correct solution is to invoke a kernel-exported CPU-specific helper
> function in the ARM kernel helper page.
>
> I see a __kuser_memory_barrier entry there which maps to smp_dmb.
That is indeed the correct way to do this - otherwise user programs will
be tied to particular architecture versions, and either an undefined
instruction fault will happen, or worse, the desired effect will not
happen.
next prev parent reply other threads:[~2009-12-11 21:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 9:20 [PATCH 1/2] perf tools: allow building for ARM Jamie Iles
2009-12-11 9:21 ` [PATCH 2/2] perf tools: allow cross compiling Jamie Iles
2009-12-11 10:27 ` [tip:perf/urgent] perf tools: Allow " tip-bot for Jamie Iles
2009-12-11 12:20 ` [PATCH] perf tools: allow building for ARM (patch v2) Jamie Iles
2009-12-11 12:54 ` [tip:perf/urgent] perf tools: Allow building for ARM tip-bot for Jamie Iles
2009-12-11 13:04 ` Jamie Iles
2009-12-11 13:26 ` Ingo Molnar
2009-12-11 10:23 ` [PATCH 1/2] perf tools: allow " Ingo Molnar
2009-12-11 10:30 ` Jamie Iles
2009-12-11 10:38 ` Ingo Molnar
2009-12-11 11:01 ` Jamie Iles
2009-12-11 11:26 ` Mikael Pettersson
2009-12-11 21:22 ` Russell King - ARM Linux [this message]
[not found] ` <000101ca7a50$b3e2ad70$1ba80850$@deacon@arm.com>
2009-12-11 11:02 ` Ingo Molnar
2009-12-11 11:08 ` Pekka Enberg
2009-12-11 10:38 ` David Miller
2009-12-11 10:41 ` Ingo Molnar
2009-12-11 11:48 ` Jamie Iles
2009-12-11 12:48 ` Ingo Molnar
2009-12-11 21:19 ` Russell King - ARM Linux
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=20091211212222.GD12628@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=jamie.iles@picochip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mingo@elte.hu \
--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