The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] timers/cleanups for v7.3-rc1
Date: Wed, 19 Aug 2026 22:59:36 +0200	[thread overview]
Message-ID: <87a4qhkerr.ffs@fw13> (raw)
In-Reply-To: <20260819184803.GA3333711@ax162>

On Wed, Aug 19 2026 at 11:48, Nathan Chancellor wrote:
>> -int read_current_timer(unsigned long *timer_val)
>> +bool delay_read_timer(unsigned long *timer_val)
>>  {
>>  	if (!delay_timer)
>> -		return -ENXIO;
>> -
>> +		return false;
>>  	*timer_val = delay_timer->read_current_timer();
>> -	return 0;
>> +	return true;
>>  }
>> -EXPORT_SYMBOL_GPL(read_current_timer);
>> +EXPORT_SYMBOL_GPL(delay_read_timer);
>>  
>>  static inline u64 cyc_to_ns(u64 cyc, u32 mult, u32 shift)
>>  {
>
> I bisected a hang that I see after getting to userspace when virtually
> testing some ARM configurations to commit dfc256dac54c ("calibrate:
> Rework delay timer calibration"). It looks like the branches in
> get_cycles() were not updated for the changed meaning of the return of
> delay_read_timer()? This appears to resolve it for me but I am not sure
> if I am missing something.
>
> diff --git a/arch/arm/include/asm/timex.h b/arch/arm/include/asm/timex.h
> index 94e40c19cfc5..4d31eab9dba2 100644
> --- a/arch/arm/include/asm/timex.h
> +++ b/arch/arm/include/asm/timex.h
> @@ -13,7 +13,7 @@ typedef unsigned long cycles_t;
>  // Temporary workaround until timex.h is cleaned up
>  bool delay_read_timer(unsigned long *t);
>  
> -#define get_cycles()	({ cycles_t c; delay_read_timer(&c) ? 0 : c; })
> +#define get_cycles()	({ cycles_t c; delay_read_timer(&c) ? c : 0; })

Duh, yes. Stupid me.

Can you please send a patch wuth a proper change log and a Fixes tag?

Thanks,

        tglx

  reply	other threads:[~2026-08-19 20:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 11:23 [GIT pull] core/entry for v7.3-rc1 Thomas Gleixner
2026-08-17 11:23 ` [GIT pull] core/rseq " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:23 ` [GIT pull] irq/core " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:23 ` [GIT pull] irq/drivers " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:23 ` [GIT pull] locking/futex " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:23 ` [GIT pull] smp/core " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:23 ` [GIT pull] timers/cleanups " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-19 18:48   ` Nathan Chancellor
2026-08-19 20:59     ` Thomas Gleixner [this message]
2026-08-19 21:44       ` Nathan Chancellor
2026-08-17 11:23 ` [GIT pull] timers/clocksource " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:24 ` [GIT pull] timers/core " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-19  1:10   ` pr-tracker-bot
2026-08-17 11:24 ` [GIT pull] timers/vdso " Thomas Gleixner
2026-08-19  1:10   ` pr-tracker-bot
2026-08-19  1:10   ` pr-tracker-bot
2026-08-19  1:10 ` [GIT pull] core/entry " pr-tracker-bot

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=87a4qhkerr.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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