[lkml]   [2013]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH v2 0/4] Add support for S3 non-stop TSC support.
Hi All,

On some new Intel Atom processors (Penwell and Cloverview), there is
a feature that the TSC won't stop in S3, say the TSC value won't be
reset to 0 after resume. This feature makes TSC a more reliable
clocksource and could benefit the timekeeping code during system
suspend/resume cycles.

The enabling efforts include adding new flags for this feature,
modifying clocksource.c and timekeeping.c to support and utilizing

The major change to timekeeping is the way to count suspened time,
current way is trying to use the persistent clock first, and then
try the rtc if persistent clock can't do it. This patch will change
the trying order to:
suspend-nonstop clocksource -> persistent clock -> rtc

Please help to review them, thanks a lot!

* Dump the code changing a clocksource's mult and shit,
as suggested by John to not hurt accuracy
* Modify the CPU feature flag name to be consistent with
other flags
* Solve the problem of judging S3/S4, as the clocksource
counter will be reset after coming out S4.

- Feng

Feng Tang (4):
x86: Add cpu capability flag X86_FEATURE_NONSTOP_TSC_S3
clocksource: Add new feature flag CLOCK_SOURCE_SUSPEND_NOTSTOP
x86: tsc: Add support for new S3_NOTSTOP feature
timekeeping: utilize the suspend-nonstop clocksource to count
suspended time

arch/x86/include/asm/cpufeature.h | 1 +
arch/x86/kernel/cpu/intel.c | 12 ++++++++
arch/x86/kernel/tsc.c | 6 +++-
include/linux/clocksource.h | 1 +
kernel/time/timekeeping.c | 57 +++++++++++++++++++++++++++++++-----
5 files changed, 68 insertions(+), 9 deletions(-)

 \ /
  Last update: 2013-03-05 04:01    [W:0.080 / U:0.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site