Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1464781 > unrolled thread

Re: [PATCH v2] clocksource: Defer override invalidation unless clock is unstable

Started byJohn Stultz <john.stultz@linaro.org>
First post2016-08-17 22:20 +0200
Last post2016-08-17 22:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v2] clocksource: Defer override invalidation unless clock  is unstable John Stultz <john.stultz@linaro.org> - 2016-08-17 22:20 +0200

#1464781 — Re: [PATCH v2] clocksource: Defer override invalidation unless clock is unstable

FromJohn Stultz <john.stultz@linaro.org>
Date2016-08-17 22:20 +0200
SubjectRe: [PATCH v2] clocksource: Defer override invalidation unless clock is unstable
Message-ID<s7ftE-5TG-5@gated-at.bofh.it>
On Sat, Aug 6, 2016 at 9:07 AM, Kyle Walker <kwalker@redhat.com> wrote:
> Clocksources don't get the VALID_FOR_HRES flag until they have been
> checked by a watchdog. However, when using an override, the
> clocksource_select logic will clear the override value if the
> clocksource is not marked VALID_FOR_HRES during that inititial check.
> When using the boot arguments clocksource=<foo>, this selection can
> run before the watchdog, and can cause the override to be incorrectly
> cleared.
>
> To address this condition, the override_name is only invalidated for
> unstable clocksources. Otherwise, the override is left intact until after
> the watchdog has validated the clocksource as stable/unstable.
>
> Signed-off-by: Kyle Walker <kwalker@redhat.com>

Queued for testing and targeting 4.9

thanks
-john

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web