Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
32 lines (29 sloc) 1.48 KB
amazon_s3_presentation_url amazon_s3_video_url author categories comments date image layout session_id session_track slideshare_presentation_url speakers title youtube_video_url tag
connect
yvr18
true
2018-09-16 09:00:00+00:00
featured file_name path
true
YVR18-409.png
/assets/images/featured-images/YVR18-409.png
resource-post
YVR18-409
None
biography company job-title name speaker-image
""
Unisoc
Software Engineer
Baolin Wang
BaolinWang.jpg
YVR18-409:Suspend time compensation for Linux kernel
session

On some hardware with multiple clocksources, we have coarse grained clocksources that support the CLOCK_SOURCE_SUSPEND_NONSTOP flag, but which are less than ideal for timekeeping whereas other clocksources can be better candidates but halt on suspend.

Currently, the timekeeping core only supports timing suspend using CLOCK_SOURCE_SUSPEND_NONSTOP clocksources if that clocksource is the current clocksource for timekeeping.

As a result, some architectures try to implement read_persistent_clock64() using those non-stop clocksources, but isn't really ideal, which will introduce more duplicate code. To fix this, provide logic to allow a registered SUSPEND_NONSTOP clocksource, which isn't the current clocksource, to be used to calculate the suspend time.

You can’t perform that action at this time.