From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 0/4] ARM: VDSO
Date: Wed, 25 Mar 2015 08:21:13 -0500 [thread overview]
Message-ID: <5512B649.5050306@mentor.com> (raw)
In-Reply-To: <20150325101004.GX8656@n2100.arm.linux.org.uk>
On 03/25/2015 05:10 AM, Russell King - ARM Linux wrote:
> On Fri, Mar 20, 2015 at 04:13:19PM -0500, Nathan Lynch wrote:
>> Provide fast userspace implementations of gettimeofday and
>> clock_gettime on systems that implement the generic timers extension
>> defined in ARMv7. This follows the example of arm64 in conception but
>> significantly differs in some aspects of the implementation (C vs
>> assembly, mainly).
>
> Okay, having re-read the code, I'm happy with this now. I'll see about
> testing it out on the platforms I have here in the next few days. As
> I now have a Cortex A15 platform, I can hopefully also check what effect
> it has there (assuming ethernet gets fixed on it so I can get programs
> onto the platform.)
Thanks Russell, I'll put it in the patch tracker today.
I'll follow up with a link to the glibc patch when I post that too.
next prev parent reply other threads:[~2015-03-25 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 21:13 [PATCH v11 0/4] ARM: VDSO Nathan Lynch
2015-03-20 21:13 ` [PATCH v11 1/4] ARM: miscellaneous vdso infrastructure, preparation Nathan Lynch
2015-03-20 21:13 ` [PATCH v11 2/4] ARM: add VDSO user-space code Nathan Lynch
2015-03-20 21:13 ` [PATCH v11 3/4] ARM: VDSO initialization, mapping, and synchronization Nathan Lynch
2015-03-20 21:13 ` [PATCH v11 4/4] ARM: add CONFIG_VDSO Kconfig and Makefile bits Nathan Lynch
2015-03-25 10:10 ` [PATCH v11 0/4] ARM: VDSO Russell King - ARM Linux
2015-03-25 13:21 ` Nathan Lynch [this message]
2015-04-03 17:50 ` Nathan Lynch
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=5512B649.5050306@mentor.com \
--to=nathan_lynch@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).