The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: song@kernel.org, joel.granados@kernel.org, dianders@chromium.org,
	cminyard@mvista.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kernel/watchdog: add /sys/kernel/{hard,soft}lockup_count
Date: Sat, 3 May 2025 19:47:06 -0700	[thread overview]
Message-ID: <20250503194706.d9e775fe8b24ad357cc6db89@linux-foundation.org> (raw)
In-Reply-To: <20250502103905.3995477-1-max.kellermann@ionos.com>

On Fri,  2 May 2025 12:39:04 +0200 Max Kellermann <max.kellermann@ionos.com> wrote:

> There is /proc/sys/kernel/hung_task_detect_count,
> /sys/kernel/warn_count and /sys/kernel/oops_count but there is no
> userspace-accessible counter for hard/soft lockups.

Documenation/, please?

>  Having this is useful for monitoring tools.

Useful how?  Use cases?  Examples?

A proposal to permanently extend Linux's userspace API requires better
justification than an unsubstantiated assertion, surely?

  parent reply	other threads:[~2025-05-04  2:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 10:39 [PATCH 1/2] kernel/watchdog: add /sys/kernel/{hard,soft}lockup_count Max Kellermann
2025-05-02 10:39 ` [PATCH 2/2] kernel/rcu/tree_stall: add /sys/kernel/rcu_stall_count Max Kellermann
2025-05-02 14:39 ` [PATCH 1/2] kernel/watchdog: add /sys/kernel/{hard,soft}lockup_count Doug Anderson
2025-05-02 15:12   ` Max Kellermann
2025-05-04  2:47 ` Andrew Morton [this message]
2025-05-04  6:36   ` Max Kellermann
2025-05-04  6:54     ` Andrew Morton

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=20250503194706.d9e775fe8b24ad357cc6db89@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cminyard@mvista.com \
    --cc=dianders@chromium.org \
    --cc=joel.granados@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.kellermann@ionos.com \
    --cc=song@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox