On Mon, Jan 20, 2020 at 06:08:23PM +0100, Christophe Leroy wrote:
> Not easy I think.
>
> First we have the unavoidable ASM entry function that can't be dropped
> because of the CR[SO] bit the set on error or clear on no error and that
> can't be done in C.
Yup.
> In our ASM VDSO, fixed
Le 20/01/2020 à 16:19, Segher Boessenkool a écrit :
On Mon, Jan 20, 2020 at 02:56:00PM +, Christophe Leroy wrote:
Nice! Much better.
It should be tested on more representative hardware, too, but this looks
promising alright :-)
mpc832x (e300c2 core) at 333 MHz:
Before:
On Mon, Jan 20, 2020 at 02:56:00PM +, Christophe Leroy wrote:
> >Nice! Much better.
> >
> >It should be tested on more representative hardware, too, but this looks
> >promising alright :-)
>
> mpc832x (e300c2 core) at 333 MHz:
>
> Before:
>
> gettimeofday:vdso: 235 nsec/call
>
Hi
On 01/17/2020 08:58 AM, Segher Boessenkool wrote:
Hi!
On Thu, Jan 16, 2020 at 05:58:24PM +, Christophe Leroy wrote:
On a powerpc8xx, with current powerpc/32 ASM VDSO:
gettimeofday:vdso: 907 nsec/call
clock-getres-realtime:vdso: 484 nsec/call
clock-gettime-realtime:vdso:
Le 17/01/2020 à 09:58, Segher Boessenkool a écrit :
Hi!
On Thu, Jan 16, 2020 at 05:58:24PM +, Christophe Leroy wrote:
On a powerpc8xx, with current powerpc/32 ASM VDSO:
gettimeofday:vdso: 907 nsec/call
clock-getres-realtime:vdso: 484 nsec/call
clock-gettime-realtime:vdso:
Hi!
On Thu, Jan 16, 2020 at 05:58:24PM +, Christophe Leroy wrote:
> On a powerpc8xx, with current powerpc/32 ASM VDSO:
>
> gettimeofday:vdso: 907 nsec/call
> clock-getres-realtime:vdso: 484 nsec/call
> clock-gettime-realtime:vdso: 899 nsec/call
>
> The first patch adds VDSO
