mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bitao Hu <yaoma@linux.alibaba.com>
To: dianders@chromium.org, akpm@linux-foundation.org,
	pmladek@suse.com, lecopzer.chen@mediatek.com,
	kernelfans@gmail.com, liusong@linux.alibaba.com
Cc: linux-kernel@vger.kernel.org, yaoma@linux.alibaba.com
Subject: [PATCHv2 0/2] *** Detect interrupt storm in softlockup ***
Date: Tue, 30 Jan 2024 15:47:42 +0800	[thread overview]
Message-ID: <20240130074744.45759-1-yaoma@linux.alibaba.com> (raw)

I have implemented a low-overhead method for detecting interrupt storm
in softlockup. Please review it, all comments are welcome.

Changes from v1 to v2:

- From Douglas, optimize the memory of cpustats. With the maximum number
of CPUs, that's now this.
2 * 8192 * 4 + 1 * 8192 * 5 * 4 + 1 * 8192 = 237,568 bytes.

- From Liu Song, refactor the code format and add necessary comments. 

- From Douglas, use interrupt counts instead of interrupt time to
determine the cause of softlockup. 

- Remove the cmdline parameter added in PATCHv1.

Bitao Hu (2):
  watchdog/softlockup: low-overhead detection of interrupt storm
  watchdog/softlockup: report the most frequent interrupts

 kernel/watchdog.c | 222 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 222 insertions(+)

-- 
2.37.1 (Apple Git-137.1)


             reply	other threads:[~2024-01-30  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  7:47 Bitao Hu [this message]
2024-01-30  7:47 ` [PATCHv2 1/2] watchdog/softlockup: low-overhead detection of interrupt storm Bitao Hu
2024-01-31  1:19   ` Liu Song
2024-01-31 11:06     ` Bitao Hu
2024-01-31  4:28   ` kernel test robot
2024-01-30  7:47 ` [PATCHv2 2/2] watchdog/softlockup: report the most frequent interrupts Bitao Hu
2024-01-31  1:50   ` Liu Song
2024-01-31 11:08     ` Bitao Hu

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=20240130074744.45759-1-yaoma@linux.alibaba.com \
    --to=yaoma@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=dianders@chromium.org \
    --cc=kernelfans@gmail.com \
    --cc=lecopzer.chen@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liusong@linux.alibaba.com \
    --cc=pmladek@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®