[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9459f1133f7e110ef882401f4bc1b9c1cd517599.camel@siemens.com>
Date: Thu, 22 Jan 2026 10:00:05 +0000
From: "Sverdlin, Alexander" <alexander.sverdlin@...mens.com>
To: "thomas.weissschuh@...utronix.de" <thomas.weissschuh@...utronix.de>
CC: "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"chleroy@...nel.org" <chleroy@...nel.org>
Subject: Re: [PATCH] powerpc/vdso: Provide clock_getres_time64()
Thanks for the quick reply, Thomas!
On Thu, 2026-01-22 at 10:50 +0100, Thomas Weißschuh wrote:
> > > For consistency with __vdso_clock_gettime64() there should also be a
> > > 64-bit variant of clock_getres(). This will allow the extension of
> > > CONFIG_COMPAT_32BIT_TIME to the vDSO and finally the removal of 32-bit
> > > time types from the kernel and UAPI.
> > >
> > > Signed-off-by: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
> >
> > I've bisected this patch to cause the following build failure on my side:
> >
> > LDS arch/powerpc/kernel/vdso/vdso32.lds
> > VDSO32A arch/powerpc/kernel/vdso/sigtramp32-32.o
> > VDSO32A arch/powerpc/kernel/vdso/gettimeofday-32.o
> > VDSO32A arch/powerpc/kernel/vdso/datapage-32.o
> > VDSO32A arch/powerpc/kernel/vdso/cacheflush-32.o
> > VDSO32A arch/powerpc/kernel/vdso/note-32.o
> > VDSO32A arch/powerpc/kernel/vdso/getcpu-32.o
> > VDSO32A arch/powerpc/kernel/vdso/getrandom-32.o
> > VDSO32A arch/powerpc/kernel/vdso/vgetrandom-chacha-32.o
> > VDSO32C arch/powerpc/kernel/vdso/vgettimeofday-32.o
> > VDSO32C arch/powerpc/kernel/vdso/vgetrandom-32.o
> > VDSO32A arch/powerpc/kernel/vdso/crtsavres-32.o
> > VDSO32L arch/powerpc/kernel/vdso/vdso32.so.dbg
> > arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not supported
> > make[2]: *** [arch/powerpc/kernel/vdso/Makefile:79: arch/powerpc/kernel/vdso/vdso32.so.dbg] Error 1
> > make[1]: *** [arch/powerpc/Makefile:388: vdso_prepare] Error 2
>
> Thanks for the report!
>
> > Does it ring any bells? What could I try/test?
>
> Not immediately, but I'll look into it.
>
> > I'm using gcc-15.2.0 and binutils 2.45.1.
>
> Is this a toolchain from https://cdn.kernel.org/pub/tools/crosstool/ ?
It's actually yocto master toolchain as of 6145837147dc2a6d54a221f9cd7fe90d6895ff90 (openembedded-core).
> Could you also share your configuration?
Do you mean kernel config? I'll send it privately in a minute not to overload the lists...
--
Alexander Sverdlin
Siemens AG
www.siemens.com
Powered by blists - more mailing lists