From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH v2] ARM: vDSO gettimeofday using generic timer architecture
Date: Mon, 10 Feb 2014 17:57:19 -0600 [thread overview]
Message-ID: <52F9675F.1040403@mentor.com> (raw)
In-Reply-To: <20140209102023.GL26684@n2100.arm.linux.org.uk>
On 02/09/2014 04:20 AM, Russell King - ARM Linux wrote:
> On Fri, Feb 07, 2014 at 05:05:49PM -0600, Nathan Lynch wrote:
>> + /* Grab the vDSO code pages. */
>> + for (i = 0; i < vdso_pages; i++) {
>> + pg = virt_to_page(&vdso_start + i*PAGE_SIZE);
>> + ClearPageReserved(pg);
>> + get_page(pg);
>> + vdso_pagelist[i] = pg;
>> + }
>
> Why do we want to clear the reserved status? This looks over complicated
> to me.
>
>> +
>> + /* Sanity check the shared object header. */
>> + vbase = vmap(vdso_pagelist, 1, 0, PAGE_KERNEL);
>> + if (vbase == NULL) {
>> + pr_err("Failed to map vDSO pagelist!\n");
>> + return -ENOMEM;
>> + } else if (memcmp(vbase, "\177ELF", 4)) {
>> + pr_err("vDSO is not a valid ELF object!\n");
>> + ret = -EINVAL;
>> + goto unmap;
>> + }
>
> Why do we need to vmap() pages which are already accessible - vdso_start
> must be part of the kernel image, and therefore will be accessible via
> standard mappings.
Right, this stuff doesn't appear to be necessary. Removed the vmap,
get_page, and ClearPageReserved calls for v3.
>> +static long clock_gettime_fallback(clockid_t _clkid, struct timespec *_ts)
>> +{
>> + register struct timespec *ts asm("r1") = _ts;
>> + register clockid_t clkid asm("r0") = _clkid;
>> + register long ret asm ("r0");
>> + register long nr asm("r7") = __NR_clock_gettime;
>> +
>> + asm("swi #0" : "=r" (ret) : "r" (clkid), "r" (ts), "r" (nr) : "memory");
>
> This isn't compatible with OABI, so either this must not be enabled when
> AEABI is disabled, or this needs to be fixed.
Okay. I'll plan on making the vdso code depend on CONFIG_AEABI, likely
indirectly via a CONFIG_VDSO Kconfig option. Since you'll need an
updated C library to actually benefit from the vdso, I doubt any OABI
support in this code would get any use.
Thanks for reviewing.
next prev parent reply other threads:[~2014-02-10 23:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 23:05 [RFC/PATCH v2] ARM: vDSO gettimeofday using generic timer architecture Nathan Lynch
2014-02-09 10:20 ` Russell King - ARM Linux
2014-02-10 16:51 ` Steve Capper
2014-02-10 17:12 ` Russell King - ARM Linux
2014-02-11 8:44 ` Steve Capper
2014-02-10 23:57 ` Nathan Lynch [this message]
2014-02-11 10:45 ` Will Deacon
2014-02-11 16:23 ` 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=52F9675F.1040403@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 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.