From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/6] ARM: allow user access to arch timer virtual counter
Date: Wed, 23 Apr 2014 18:32:45 +0100 [thread overview]
Message-ID: <20140423173244.GL5649@arm.com> (raw)
In-Reply-To: <10ed3f4cfce13a80a9a3070934fc0e31619a1242.1398213562.git.nathan_lynch@mentor.com>
On Wed, Apr 23, 2014 at 01:48:53AM +0100, Nathan Lynch wrote:
> As ARM64 does. This is a necessary prerequisite for implementing
> gettimeofday and clock_gettime in a vdso.
Doesn't this change make arch_counter_set_user_access identical for arm and
arm64? In which case, we could move it into the driver itself.
Will
next prev parent reply other threads:[~2014-04-23 17:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 0:48 [PATCH v6 0/6] ARM: vdso gettimeofday using generic timer architecture Nathan Lynch
2014-04-23 0:48 ` [PATCH v6 1/6] ARM: place sigpage at a random offset above stack Nathan Lynch
2014-04-23 0:48 ` [PATCH v6 2/6] ARM: allow user access to arch timer virtual counter Nathan Lynch
2014-04-23 17:32 ` Will Deacon [this message]
2014-04-23 17:41 ` Nathan Lynch
2014-04-24 10:18 ` Will Deacon
2014-04-23 0:48 ` [PATCH v6 3/6] ARM: miscellaneous vdso infrastructure, preparation Nathan Lynch
2014-04-23 0:48 ` [PATCH v6 4/6] ARM: add vdso user-space code Nathan Lynch
2014-04-23 0:48 ` [PATCH v6 5/6] ARM: vdso initialization, mapping, and synchronization Nathan Lynch
2014-04-23 0:48 ` [PATCH v6 6/6] ARM: add CONFIG_VDSO Kconfig and Makefile bits Nathan Lynch
2014-04-23 19:45 ` [PATCH v6 0/6] ARM: vdso gettimeofday using generic timer architecture Stephen Boyd
2014-04-24 2:28 ` Nathan Lynch
2014-04-24 17:00 ` Stephen Boyd
2014-04-23 21:50 ` Russell King - ARM Linux
2014-04-24 7:37 ` Ard Biesheuvel
2014-04-24 15:15 ` Nathan Lynch
2014-04-24 15:25 ` Ard Biesheuvel
2014-04-24 14:59 ` Nathan Lynch
2014-04-24 16:22 ` Russell King - ARM Linux
2014-04-24 18:41 ` Nathan Lynch
2014-04-24 18:45 ` 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=20140423173244.GL5649@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@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 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.