[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160429160154.GC30316@e104818-lin.cambridge.arm.com>
Date: Fri, 29 Apr 2016 17:01:55 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Yury Norov <ynorov@...iumnetworks.com>
Cc: arnd@...db.de, 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 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.
> +$(obj)/sigreturn-ilp32.o: $(src)/../vdso/sigreturn.S
> + $(call if_changed_dep,vdso-ilp32as)
This one should be fine because ILP32 uses the same generic
__NR_rt_sigreturn syscall number.
--
Catalin
Powered by blists - more mailing lists