From: Thomas Gleixner <tglx@linutronix.de>
To: Bitao Hu <yaoma@linux.alibaba.com>,
dianders@chromium.org, liusong@linux.alibaba.com,
akpm@linux-foundation.org, pmladek@suse.com,
kernelfans@gmail.com, deller@gmx.de, npiggin@gmail.com,
tsbogend@alpha.franken.de, James.Bottomley@HansenPartnership.com,
jan.kiszka@siemens.com
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
yaoma@linux.alibaba.com
Subject: Re: [PATCHv12 1/4] genirq: Provide a snapshot mechanism for interrupt statistics
Date: Tue, 09 Apr 2024 11:58:34 +0200 [thread overview]
Message-ID: <87frvu7t85.ffs@tglx> (raw)
In-Reply-To: <20240306125208.71803-2-yaoma@linux.alibaba.com>
On Wed, Mar 06 2024 at 20:52, Bitao Hu wrote:
> The soft lockup detector lacks a mechanism to identify interrupt storms
> as root cause of a lockup. To enable this the detector needs a
> mechanism to snapshot the interrupt count statistics on a CPU when the
> detector observes a potential lockup scenario and compare that against
> the interrupt count when it warns about the lockup later on. The number
> of interrupts in that period give a hint whether the lockup might be
> caused by an interrupt storm.
>
> Instead of having extra storage in the lockup detector and accessing
> the internals of the interrupt descriptor directly, convert the per CPU
> irq_desc::kstat_irq member to a data structure which contains the
> counter plus a snapshot member and provide interfaces to take a
> snapshot of all interrupts on the current CPU and to retrieve the delta
> of a specific interrupt later on.
>
> Originally-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Bitao Hu <yaoma@linux.alibaba.com>
> Reviewed-by: Liu Song <liusong@linux.alibaba.com>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
This does not apply anymore.
Also can you please split this apart to convert kstat_irqs to a struct
with just the count in it and then add the snapshot mechanics on top.
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Bitao Hu <yaoma@linux.alibaba.com>,
dianders@chromium.org, liusong@linux.alibaba.com,
akpm@linux-foundation.org, pmladek@suse.com,
kernelfans@gmail.com, deller@gmx.de, npiggin@gmail.com,
tsbogend@alpha.franken.de, James.Bottomley@HansenPartnership.com,
jan.kiszka@siemens.com
Cc: yaoma@linux.alibaba.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCHv12 1/4] genirq: Provide a snapshot mechanism for interrupt statistics
Date: Tue, 09 Apr 2024 11:58:34 +0200 [thread overview]
Message-ID: <87frvu7t85.ffs@tglx> (raw)
In-Reply-To: <20240306125208.71803-2-yaoma@linux.alibaba.com>
On Wed, Mar 06 2024 at 20:52, Bitao Hu wrote:
> The soft lockup detector lacks a mechanism to identify interrupt storms
> as root cause of a lockup. To enable this the detector needs a
> mechanism to snapshot the interrupt count statistics on a CPU when the
> detector observes a potential lockup scenario and compare that against
> the interrupt count when it warns about the lockup later on. The number
> of interrupts in that period give a hint whether the lockup might be
> caused by an interrupt storm.
>
> Instead of having extra storage in the lockup detector and accessing
> the internals of the interrupt descriptor directly, convert the per CPU
> irq_desc::kstat_irq member to a data structure which contains the
> counter plus a snapshot member and provide interfaces to take a
> snapshot of all interrupts on the current CPU and to retrieve the delta
> of a specific interrupt later on.
>
> Originally-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Bitao Hu <yaoma@linux.alibaba.com>
> Reviewed-by: Liu Song <liusong@linux.alibaba.com>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
This does not apply anymore.
Also can you please split this apart to convert kstat_irqs to a struct
with just the count in it and then add the snapshot mechanics on top.
Thanks,
tglx
next prev parent reply other threads:[~2024-04-09 9:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 12:52 [PATCHv12 0/4] *** Detect interrupt storm in softlockup *** Bitao Hu
2024-03-06 12:52 ` Bitao Hu
2024-03-06 12:52 ` [PATCHv12 1/4] genirq: Provide a snapshot mechanism for interrupt statistics Bitao Hu
2024-03-06 12:52 ` Bitao Hu
2024-04-09 9:58 ` Thomas Gleixner [this message]
2024-04-09 9:58 ` Thomas Gleixner
2024-04-10 6:45 ` Bitao Hu
2024-04-10 6:45 ` Bitao Hu
2024-04-10 14:17 ` Thomas Gleixner
2024-04-10 14:17 ` Thomas Gleixner
2024-03-06 12:52 ` [PATCHv12 2/4] genirq: Avoid summation loops for /proc/interrupts Bitao Hu
2024-03-06 12:52 ` Bitao Hu
2024-03-06 12:52 ` [PATCHv12 3/4] watchdog/softlockup: low-overhead detection of interrupt storm Bitao Hu
2024-03-06 12:52 ` Bitao Hu
2024-03-06 12:52 ` [PATCHv12 4/4] watchdog/softlockup: report the most frequent interrupts Bitao Hu
2024-03-06 12:52 ` Bitao Hu
2024-03-23 20:43 ` Thomas Gleixner
2024-03-23 20:43 ` Thomas Gleixner
2024-03-25 9:47 ` Bitao Hu
2024-03-25 9:47 ` Bitao Hu
2024-04-01 16:41 ` Doug Anderson
2024-04-01 16:41 ` Doug Anderson
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=87frvu7t85.ffs@tglx \
--to=tglx@linutronix.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=dianders@chromium.org \
--cc=jan.kiszka@siemens.com \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liusong@linux.alibaba.com \
--cc=npiggin@gmail.com \
--cc=pmladek@suse.com \
--cc=tsbogend@alpha.franken.de \
--cc=yaoma@linux.alibaba.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.