All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: 刘琦 <liuqi405@icloud.com>
Cc: daniel.lezcano@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	quic_ylal@quicinc.com, stable@vger.kernel.org, will@kernel.org,
	王法杰 <wangfajie@longcheer.com>,
	liurenwang@longcheer.com, zhanghui5@longcheer.com,
	liangke1@xiaomi.com
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround
Date: Thu, 19 Jan 2023 09:52:16 +0000	[thread overview]
Message-ID: <6ea81f6e27a3ec4a61088da045da053b@kernel.org> (raw)
In-Reply-To: <757D0727-BB99-4FB0-8A7C-70410E9D7BAD@icloud.com>

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@longcheer.com>
> Tested-by: liurenwang <liurenwang@longcheer.com>
> Tested-by: zhanghui <zhanghui5@longcheer.com>
> Tested-by: liangke <liangke1@xiaomi.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...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: 刘琦 <liuqi405@icloud.com>
Cc: daniel.lezcano@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	quic_ylal@quicinc.com, stable@vger.kernel.org, will@kernel.org,
	王法杰 <wangfajie@longcheer.com>,
	liurenwang@longcheer.com, zhanghui5@longcheer.com,
	liangke1@xiaomi.com
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround
Date: Thu, 19 Jan 2023 09:52:16 +0000	[thread overview]
Message-ID: <6ea81f6e27a3ec4a61088da045da053b@kernel.org> (raw)
In-Reply-To: <757D0727-BB99-4FB0-8A7C-70410E9D7BAD@icloud.com>

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@longcheer.com>
> Tested-by: liurenwang <liurenwang@longcheer.com>
> Tested-by: zhanghui <zhanghui5@longcheer.com>
> Tested-by: liangke <liangke1@xiaomi.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...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-01-20  5:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  7:59 [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround 刘琦
2023-01-19  9:52 ` Marc Zyngier [this message]
2023-01-19  9:52   ` Marc Zyngier
  -- strict thread matches above, loose matches on Subject: below --
2023-01-19 13:28 王法杰
2023-01-13 11:16 Marc Zyngier
2023-01-13 11:16 ` Marc Zyngier
2023-01-13 12:45 ` Mark Rutland
2023-01-13 12:45   ` Mark Rutland
2023-03-28 13:59 ` Will Deacon
2023-03-28 13:59   ` Will Deacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ea81f6e27a3ec4a61088da045da053b@kernel.org \
    --to=maz@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=liangke1@xiaomi.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuqi405@icloud.com \
    --cc=liurenwang@longcheer.com \
    --cc=mark.rutland@arm.com \
    --cc=quic_ylal@quicinc.com \
    --cc=stable@vger.kernel.org \
    --cc=wangfajie@longcheer.com \
    --cc=will@kernel.org \
    --cc=zhanghui5@longcheer.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.