From: Stefani Seibold <stefani@seibold.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VDSO support for 32bit time functions
Date: Tue, 21 Jan 2014 21:54:06 +0100 [thread overview]
Message-ID: <1390337646.1613.12.camel@wall-e.seibold.net> (raw)
In-Reply-To: <20140121075123.GA32170@kroah.com>
Hi Grek,
On Monday, the 20.01.2014, 23:51 -0800 wrote Greg KH:
> Hi Stefani,
>
> About a year ago you posted a big patch to implement VDSO support for
> 32bit functions, and the response was a request to clean it up a bit by
> breaking up the generic bits into a series to make it easier to review /
> apply.
>
> The patch I'm referring to can be found here:
> http://thread.gmane.org/gmane.linux.kernel/1411713
>
> Did that ever happen?
>
I have revamped the patch, but the request for the IA32_EMULATION is
still pending. I have now a solution for this which i had already
implemented, but i need to do some tests.
> If not, any specific reason why? Do you have a newer version somewhere
> for "modern" kernel versions?
>
Currently my latest version is for 3.10, but i think i can bring it to
3.13. I will do this next weekend and post the patch.
> If you're not interested in this anymore, mind if I take it up based on
> your last version?
>
I am interested since i must port again and again to the next kernel
version for my devices.
Your support will be welcome.
> I'm getting some complaints that this type of thing would really be good
> as 32bit gettimeofday() on 64bit kernels is really slow (65 nanoseconds
> on 32bit vs. 17 nanoseconds on 64bit on a high-end i7 processor.)
>
Stay tune until next week.
- Stefani
next prev parent reply other threads:[~2014-01-21 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 7:51 VDSO support for 32bit time functions Greg KH
2014-01-21 20:54 ` Stefani Seibold [this message]
2014-01-22 1:34 ` Greg KH
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=1390337646.1613.12.camel@wall-e.seibold.net \
--to=stefani@seibold.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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.