[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1554541.oDP7Ro5zB2@wuerfel>
Date: Fri, 29 Apr 2016 19:30:19 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Yury Norov <ynorov@...iumnetworks.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, linux-s390@...r.kernel.org,
pinskia@...il.com, Prasun.Kapoor@...iumnetworks.com,
schwab@...e.de, broonie@...nel.org, linux-doc@...r.kernel.org,
heiko.carstens@...ibm.com, agraf@...e.de, klimov.linux@...il.com,
bamvor.zhangjian@...wei.com, schwidefsky@...ibm.com,
Nathan_Lynch@...tor.com,
Philipp Tomsich <philipp.tomsich@...obroma-systems.com>,
joseph@...esourcery.com, christoph.muellner@...obroma-systems.com
Subject: Re: [PATCH 24/25] arm64:ilp32: add vdso-ilp32 and use for signal return
On Friday 29 April 2016 17:01:55 Catalin Marinas wrote:
> On Wed, Apr 06, 2016 at 01:08:46AM +0300, Yury Norov wrote:
> > ILP32 VDSO exports next symbols:
> > __kernel_rt_sigreturn;
> > __kernel_gettimeofday;
> > __kernel_clock_gettime;
> > __kernel_clock_getres;
>
> [...]
>
> > +$(obj)/gettimeofday-ilp32.o: $(src)/../vdso/gettimeofday.S
> > + $(call if_changed_dep,vdso-ilp32as)
>
> Are struct timeval and timespec the same between ILP32 and LP64? For
> example, __kernel_gettimeofday() assumes TVAL_TV_SEC offset defined in
> asm-offsets.c based on the LP64 timeval.
No, ilp32 uses the generic 32-bit data structures, which have a 32-bit
time_t. I guess that means it can work for little-endian but not
big-endian, right?
Arnd
Powered by blists - more mailing lists