sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andy Lutomirski <luto@kernel.org>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	 "David S . Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	 Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com>,
	Nick Alcock <nick.alcock@oracle.com>,
	 John Stultz <jstultz@google.com>,
	Stephen Boyd <sboyd@kernel.org>,
	 John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 12/13] sparc64: vdso: Implement clock_getres()
Date: Fri, 15 Aug 2025 14:34:49 +0200	[thread overview]
Message-ID: <20250815142418-d28c6551-bec1-4a65-9c52-f1afd7b630ed@linutronix.de> (raw)
In-Reply-To: <bf9ec82b-af1b-4684-ada5-8529b7ceb06a@app.fastmail.com>

On Fri, Aug 15, 2025 at 02:13:46PM +0200, Arnd Bergmann wrote:
> On Fri, Aug 15, 2025, at 12:41, Thomas Weißschuh wrote:
> > 
> > +#define VDSO_HAS_CLOCK_GETRES		1
> > +
> >  #ifdef	CONFIG_SPARC64
> 
> > +static __always_inline
> > +long clock_getres_fallback(clockid_t clock, struct __kernel_timespec 
> > *ts)
> 
> > +
> > +static __always_inline
> > +long clock_getres32_fallback(clockid_t clock, struct old_timespec32 
> > *ts)
> > +{
> 
> > +}
> > +#else /* !CONFIG_SPARC64 */
> > +
> > +static __always_inline
> > +long clock_getres_fallback(clockid_t clock, struct __kernel_timespec 
> > *ts)
> 
> > +
> > +#endif /* CONFIG_SPARC64 */
> > 
> 
> Something doesn't quite line up here: I think the check for
> CONFIG_SPARC64 needs to be for "#ifndef BUILD_VDSO32", since
> sparc32 kernels don't have a vdso at all yet.

arch/sparc/vdso/vdso32/vclock_gettime.c translates BUILD_VDSO32 into more
"standard" defines, CONFIG_SPARC64 in this case. I have a follow-up series
to get rid of this pattern in all architectures.

> On sparc64 kernels, I think you only need the
> clock_getres_fallback() for 64-bit userspace, while
> the compat path probably doesn't care about getres, neither
> the time32 nor time64 variant.

Why?


Thomas

  reply	other threads:[~2025-08-15 12:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 10:41 [PATCH v2 00/13] sparc64: vdso: Switch to generic vDSO library Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 01/13] vdso: Add struct __kernel_old_timeval forward declaration to gettime.h Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 02/13] sparc64: vdso: Link with -z noexecstack Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 03/13] sparc64: vdso: Remove obsolete "fake section table" reservation Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 04/13] sparc64: vdso: Replace code patching with runtime conditional Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 05/13] sparc64: vdso: Move hardware counter read into header Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 06/13] sparc64: vdso: Move syscall fallbacks " Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 07/13] sparc64: vdso: Introduce vdso/processor.h Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 08/13] sparc64: vdso: Switch to the generic vDSO library Thomas Weißschuh
2025-08-25 15:55   ` Andreas Larsson
2025-08-26  5:56     ` Thomas Weißschuh
2025-08-28 15:38       ` Andreas Larsson
2025-08-29 10:02         ` Andreas Larsson
2025-08-29 10:37           ` Thomas Weißschuh
2025-08-29 10:40             ` John Paul Adrian Glaubitz
2025-08-29 10:52               ` Thomas Weißschuh
2025-08-29 15:24                 ` John Paul Adrian Glaubitz
2025-09-01 15:17                 ` Arnd Bergmann
2025-09-02  6:21                   ` Thomas Weißschuh
2025-08-29 13:41             ` Andreas Larsson
2025-08-29 13:51               ` Thomas Weißschuh
2025-08-29 14:05               ` Thomas Weißschuh
2025-08-29 16:35                 ` Andreas Larsson
2025-08-29 17:07                   ` Thomas Weißschuh
2025-09-01 14:28                     ` Andreas Larsson
2025-09-01 14:59                       ` Thomas Weißschuh
2025-09-01 19:05                         ` Andreas Larsson
2025-08-29 15:44               ` John Paul Adrian Glaubitz
2025-08-15 10:41 ` [PATCH v2 09/13] sparc64: vdso2c: Drop sym_vvar_start handling Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 10/13] sparc64: vdso2c: Remove symbol handling Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 11/13] sparc64: vdso: Implement clock_gettime64() Thomas Weißschuh
2025-08-15 10:41 ` [PATCH v2 12/13] sparc64: vdso: Implement clock_getres() Thomas Weißschuh
2025-08-15 12:13   ` Arnd Bergmann
2025-08-15 12:34     ` Thomas Weißschuh [this message]
2025-08-15 20:09       ` Arnd Bergmann
2025-08-18  5:50         ` Thomas Weißschuh
2025-08-18  6:54           ` Arnd Bergmann
2025-08-18 13:00             ` Thomas Weißschuh
2025-08-18 13:17               ` Arnd Bergmann
2025-08-15 10:41 ` [PATCH v2 13/13] clocksource: remove ARCH_CLOCKSOURCE_DATA Thomas Weißschuh

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=20250815142418-d28c6551-bec1-4a65-9c52-f1afd7b630ed@linutronix.de \
    --to=thomas.weissschuh@linutronix.de \
    --cc=andreas@gaisler.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=nagarathnam.muthusamy@oracle.com \
    --cc=nick.alcock@oracle.com \
    --cc=sboyd@kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).