All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-kernel@vger.kernel.org, john.stultz@linaro.org
Subject: CLOCK_AUX stepping
Date: Mon, 25 Aug 2025 11:26:12 +0200	[thread overview]
Message-ID: <aKwsNNWsHJg8IKzj@localhost> (raw)

There is an issue with the new system auxiliary clocks. When I make
a larger step of a CLOCK_AUX clock (by clock_settime() or
adjtimex(ADJ_SETOFFSET)), the system slows down significantly to
almost being unusable. This didn't happen with the original
tglx/timers/ptp/driver-auxclock branch, but happens with 6.17-rc1
and later.

Reproducer:
- echo 1 > /sys/kernel/time/aux_clocks/0/aux_clock_enable
- git clone -b staging https://github.com/mlichvar/linuxptp.git
- cd linuxptp && make
- ./phc_ctl CLOCK_AUX0 set

"echo 0 > .../aux_clock_enable" revives the system.

I'm not sure if this isn't just a symptom, but the top functions
reported by perf are:
  87.10%  swapper          [kernel.kallsyms]       [k] queued_spin_lock_slowpath                                    
   6.84%  rcu_exp_gp_kthr  [kernel.kallsyms]       [k] queued_spin_lock_slowpath                                    
   1.90%  rcu_exp_gp_kthr  [kernel.kallsyms]       [k] smp_call_function_single                                     

-- 
Miroslav Lichvar


             reply	other threads:[~2025-08-25  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  9:26 Miroslav Lichvar [this message]
2025-08-25 10:22 ` CLOCK_AUX stepping Thomas Weißschuh
2025-08-25 10:45   ` Miroslav Lichvar

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=aKwsNNWsHJg8IKzj@localhost \
    --to=mlichvar@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.