diff options
author | Anna-Maria Behnsen <anna-maria@linutronix.de> | 2024-10-09 10:29:14 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2024-10-25 19:49:15 +0200 |
commit | b2350d954dca14dfde95e7512ad521ccab0e4108 (patch) | |
tree | 713d593f87bd672b08071eb59c601bbc5a1a3b3e /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 2b473e65dea6be1a60d357f0afe46ecb6bf91501 (diff) |
timekeeping: Rework timekeeping_resume() to use shadow_timekeeper
Updates of the timekeeper can be done by operating on the shadow timekeeper
and afterwards copying the result into the real timekeeper. This has the
advantage, that the sequence count write protected region is kept as small
as possible.
While the sequence count held time is not relevant for the resume path as
there is no concurrency, there is no reason to have this function
different than all the other update sites.
Convert timekeeping_inject_offset() to use this scheme and cleanup the
variable declaration while at it.
Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: John Stultz <jstultz@google.com>
Link: https://lore.kernel.org/all/20241009-devel-anna-maria-b4-timers-ptp-timekeeping-v2-21-554456a44a15@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions