From: Alex Smith <alex.smith@imgtec.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: VDSO
Date: Thu, 13 Aug 2015 09:25:50 +0100 [thread overview]
Message-ID: <55CC548E.6090407@imgtec.com> (raw)
In-Reply-To: <55CB70EE.4080802@gmail.com>
On 12/08/2015 17:14, David Daney wrote:
> On 08/12/2015 03:21 AM, Alex Smith wrote:
>> Hi,
>>
>> I'm intending to start work on a proper VDSO implementation for MIPS that can provide user implementations of gettimeofday() and such, as well as take over from the current signal return trampoline code.
>>
>> Just wondering if there's anyone else who's doing any work towards this so we can avoid duplication of effort if so?
>>
>
> I am not working on it, but have a small laundry list of what could be done:
>
> 1) Perhaps the VA of the vdso needs to be randomized.
>
> 2) Provide proper .eh_frame data for the signal return trampolines.
>
> 3) gettimeofday (as you suggest).
Yes, I intend to do all of these.
> 4) Provide optimized versions of memcpy, etc.
Is this something that belongs in a VDSO? memcpy and friends aren't syscalls, this belongs in libc IMO. ELF HWCAP flags provided by the kernel could be used by libc to decide which CPU features it can make use of to implement them.
Thanks,
Alex
>
> David Daney
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Alex Smith <alex.smith@imgtec.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: VDSO
Date: Thu, 13 Aug 2015 09:25:50 +0100 [thread overview]
Message-ID: <55CC548E.6090407@imgtec.com> (raw)
Message-ID: <20150813082550.m-aIHcUpJRELLXQeO997EXLP_2b3LPm-ll9ki7tnENc@z> (raw)
In-Reply-To: <55CB70EE.4080802@gmail.com>
On 12/08/2015 17:14, David Daney wrote:
> On 08/12/2015 03:21 AM, Alex Smith wrote:
>> Hi,
>>
>> I'm intending to start work on a proper VDSO implementation for MIPS that can provide user implementations of gettimeofday() and such, as well as take over from the current signal return trampoline code.
>>
>> Just wondering if there's anyone else who's doing any work towards this so we can avoid duplication of effort if so?
>>
>
> I am not working on it, but have a small laundry list of what could be done:
>
> 1) Perhaps the VA of the vdso needs to be randomized.
>
> 2) Provide proper .eh_frame data for the signal return trampolines.
>
> 3) gettimeofday (as you suggest).
Yes, I intend to do all of these.
> 4) Provide optimized versions of memcpy, etc.
Is this something that belongs in a VDSO? memcpy and friends aren't syscalls, this belongs in libc IMO. ELF HWCAP flags provided by the kernel could be used by libc to decide which CPU features it can make use of to implement them.
Thanks,
Alex
>
> David Daney
>
>
next prev parent reply other threads:[~2015-08-13 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 10:21 VDSO Alex Smith
2015-08-12 10:21 ` VDSO Alex Smith
2015-08-12 16:14 ` VDSO David Daney
2015-08-13 8:25 ` Alex Smith [this message]
2015-08-13 8:25 ` VDSO Alex Smith
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=55CC548E.6090407@imgtec.com \
--to=alex.smith@imgtec.com \
--cc=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.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.