> Do applications call into the vdso directly and expect to get a timespec
> out? If they always go through the C library as an intermediate, then
> the glibc clock_gettime() could do the conversion.
It is recommended that applications do not call vdso symbols directly.
According to manpage:
"If
On Wed, Nov 8, 2017 at 9:00 PM, Deepa Dinamani wrote:
> On Wed, Nov 8, 2017 at 1:37 AM, Arnd Bergmann wrote:
>> On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote:
>>
>>
>> I need some insight from Deepa and Palmer here: to prepare for 64-bit
>> time_t in the
>> future, would it make sense to d
On Wed, Nov 8, 2017 at 1:37 AM, Arnd Bergmann wrote:
> On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote:
>
>> --- /dev/null
>> +++ b/arch/nds32/include/asm/vdso_datapage.h
>> @@ -0,0 +1,51 @@
>
>> +#ifndef __ASM_VDSO_DATAPAGE_H
>> +#define __ASM_VDSO_DATAPAGE_H
>> +
>> +#ifdef __KERNEL__
>> +
>
On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote:
> --- /dev/null
> +++ b/arch/nds32/include/asm/vdso_datapage.h
> @@ -0,0 +1,51 @@
> +#ifndef __ASM_VDSO_DATAPAGE_H
> +#define __ASM_VDSO_DATAPAGE_H
> +
> +#ifdef __KERNEL__
> +
> +#ifndef __ASSEMBLY__
> +
> +struct vdso_data {
> + bool cy
From: Greentime Hu
Signed-off-by: Vincent Chen
Signed-off-by: Greentime Hu
---
arch/nds32/include/asm/vdso.h | 35
arch/nds32/include/asm/vdso_datapage.h | 51 ++
arch/nds32/kernel/vdso.c | 243 ++
arch/nds32/kernel/vdso/
