Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
MIME-Version: 1.0
References: <20231123084022.10302-1-lizhe.67@bytedance.com>
In-Reply-To: <20231123084022.10302-1-lizhe.67@bytedance.com>
From:   Doug Anderson <dianders@chromium.org>
Date:   Mon, 27 Nov 2023 13:47:58 -0800
Message-ID: <CAD=FV=Ux09EUZwpW3tYFEYG=LfYDibmHrgczF03_EszLykagUQ@mail.gmail.com>
Subject: Re: [PATCH v3] softlockup: serialized softlockup's log
To:     lizhe.67@bytedance.com
Cc:     akpm@linux-foundation.org, pmladek@suse.com,
        lecopzer.chen@mediatek.com, kernelfans@gmail.com,
        linux-kernel@vger.kernel.org, lizefan.x@bytedance.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi,

On Thu, Nov 23, 2023 at 12:41=E2=80=AFAM <lizhe.67@bytedance.com> wrote:
>
> From: Li Zhe <lizhe.67@bytedance.com>
>
> If multiple CPUs trigger softlockup at the same time with
> 'softlockup_all_cpu_backtrace=3D0', the softlockup's logs will appear
> staggeredly in dmesg, which will affect the viewing of the logs for
> developer. Since the code path for outputting softlockup logs is not
> a kernel hotspot and the performance requirements for the code are
> not strict, locks are used to serialize the softlockup log output to
> improve the readability of the logs.
>
> Signed-off-by: Li Zhe <lizhe.67@bytedance.com>
> ---
> Changelogs:
>
> v1->v2:
> - define the lock outside the scope of function
> - add precondition 'softlockup_all_cpu_backtrace=3D0' in commit message
>
> v2->v3:
> - define the lock inside the scope of function
>
>  kernel/watchdog.c | 3 +++
>  1 file changed, 3 insertions(+)

Reviewed-by: Douglas Anderson <dianders@chromium.org>