From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "thomas.weissschuh@linutronix.de" <thomas.weissschuh@linutronix.de>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chleroy@kernel.org" <chleroy@kernel.org>
Subject: Re: [PATCH] powerpc/vdso: Provide clock_getres_time64()
Date: Thu, 22 Jan 2026 10:00:05 +0000 [thread overview]
Message-ID: <9459f1133f7e110ef882401f4bc1b9c1cd517599.camel@siemens.com> (raw)
In-Reply-To: <20260122104257-3124dc96-5916-4d25-bbce-9b868b30ee18@linutronix.de>
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@linutronix.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
next prev parent reply other threads:[~2026-01-22 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 7:26 [PATCH] powerpc/vdso: Provide clock_getres_time64() Thomas Weißschuh
2026-01-14 8:27 ` Christophe Leroy (CS GROUP)
2026-01-22 9:39 ` Sverdlin, Alexander
2026-01-22 9:50 ` Thomas Weißschuh
2026-01-22 10:00 ` Sverdlin, Alexander [this message]
2026-01-22 10:27 ` Christophe Leroy (CS GROUP)
2026-01-22 10:49 ` Thomas Weißschuh
2026-01-22 10:58 ` Christophe Leroy (CS GROUP)
2026-01-22 11:07 ` Thomas Weißschuh
2026-01-22 11:31 ` Christophe Leroy (CS GROUP)
2026-01-22 11:41 ` Thomas Weißschuh
2026-01-22 13:30 ` Christophe Leroy (CS GROUP)
2026-01-22 10:49 ` Christophe Leroy (CS GROUP)
2026-01-22 9:53 ` Christophe Leroy (CS GROUP)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9459f1133f7e110ef882401f4bc1b9c1cd517599.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=thomas.weissschuh@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox