Re: [RFC PATCH] clocksource: skip check while watchdog hung up or unstable
From: Thomas Gleixner
Date: Wed Aug 11 2021 - 10:01:16 EST
On Wed, Aug 11 2021 at 21:18, brookxu wrote:
> Thomas Gleixner wrote on 2021/8/11 8:44 下午:
>> On Wed, Aug 11 2021 at 17:55, brookxu wrote:
>>> From: Chunguang Xu <brookxu@xxxxxxxxxxx>
>>> After patch 1f45f1f3 (clocksource: Make clocksource validation work
>>> for all clocksources), md_nsec may be 0 in some scenarios, such as
>>> the watchdog is delayed for a long time or the watchdog has a
>> Maybe 0? There is exactly one single possibility for it to be zero:
>> cs->wd_last == wdnow, i.e. delta = 0 -> wd_nsec = 0
>> So how does that condition solve any long delay or wrap around of the
>> watchdog? It's more than unlikely to hit exactly this case where the
>> readout is identical to the previous readout unless the watchdog stopped
> Maybe I missed something. Like this example, when watchdog run ,hpet have
> wrap around:
> 'hpet' wd_now: d76e5a69 wd_last: f929eb3c mask: ffffffff
> We can calculate the number of elapsed cycles:
> cycles = wd_now - wd_last = 0xde446f2d
> clocksource_delta() uses the MSB to determine an invalid inteval and returns
> 0, but for 0xde446f2d, this judgment should be wrong.
You're right. I forgot about the MSB check which is enabled on x86.
>>> We found a problem when testing nvme disks with fio, when multiple
>>> queue interrupts of a disk were mapped to a single CPU. IO interrupt
>>> processing will cause the watchdog to be delayed for a long time
>>> (155 seconds), the system reports TSC unstable and switches the clock
>> If you hold off the softirq from running for 155 seconds then the TSC
>> watchdog is the least of your problems.
> To be precise, we are processing interrupts in handle_edge_irq() for a long
> time. Since the interrupts of multiple hardware queues are mapped to a single
> CPU, multiple cores are continuously issuing IO, and then a single core is
> processing IO. Perhaps the test case can be optimized, but shouldn't this lead
> to switching clocks in principle?
The clocksource watchdog failure is only _ONE_ consequence. Processing
hard interrupts for 155 seconds straight will trigger lockup detectors
of all sorts if you have them enabled.
So just papering over the clocksource watchdog does not solve anything,
really. Next week you have to add similar hacks to the lockup detectors,
RCU and whatever.