[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6ea81f6e27a3ec4a61088da045da053b@kernel.org>
Date: Thu, 19 Jan 2023 09:52:16 +0000
From: Marc Zyngier <maz@...nel.org>
To: 刘琦 <liuqi405@...oud.com>
Cc: daniel.lezcano@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, mark.rutland@....com,
quic_ylal@...cinc.com, stable@...r.kernel.org, will@...nel.org,
王法杰
<wangfajie@...gcheer.com>, liurenwang@...gcheer.com,
zhanghui5@...gcheer.com, liangke1@...omi.com
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock
when non-boot CPUs need counter workaround
On 2023-01-19 07:59, 刘琦 wrote:
> [Test Report]
> Result: Test Pass
>
> A total of two rounds of pending testing
> a. The first round of hanging test
> Number of machines: 200
> Hanging test duration: 48h
> Hanging test results: no walt crash problem
> b. The second round of hanging test
> Number of machines: 200
> Hanging test duration: 72h
> Hanging test results: no walt crash problem
>
> Tested-by: wangfajie <wangfajie@...gcheer.com>
> Tested-by: liurenwang <liurenwang@...gcheer.com>
> Tested-by: zhanghui <zhanghui5@...gcheer.com>
> Tested-by: liangke <liangke1@...omi.com>
Thanks for this.
The only issue here is that that you don't explain what you tested,
nor how you tested it.
It is also a patch that has known defects (you just have to read the
thread for the details)... This makes this testing, no matter how
thorough it is, rather ineffective.
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists