From: Thomas Gleixner <tglx@linutronix.de>
To: Bitao Hu <yaoma@linux.alibaba.com>,
dianders@chromium.org, pmladek@suse.com,
akpm@linux-foundation.org, kernelfans@gmail.com,
liusong@linux.alibaba.com, deller@gmx.de, npiggin@gmail.com,
jan.kiszka@siemens.com, kbingham@kernel.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kvm@vger.kernel.org, Bitao Hu <yaoma@linux.alibaba.com>
Subject: Re: [PATCHv8 2/2] watchdog/softlockup: report the most frequent interrupts
Date: Tue, 20 Feb 2024 10:35:45 +0100 [thread overview]
Message-ID: <87le7fiiku.ffs@tglx> (raw)
In-Reply-To: <20240219161920.15752-3-yaoma@linux.alibaba.com>
On Tue, Feb 20 2024 at 00:19, Bitao Hu wrote:
> arch/mips/dec/setup.c | 2 +-
> arch/parisc/kernel/smp.c | 2 +-
> arch/powerpc/kvm/book3s_hv_rm_xics.c | 2 +-
> include/linux/irqdesc.h | 9 ++-
> include/linux/kernel_stat.h | 4 +
> kernel/irq/internals.h | 2 +-
> kernel/irq/irqdesc.c | 34 ++++++--
> kernel/irq/proc.c | 9 +--
This really wants to be split into two patches. Interrupt infrastructure
first and then the actual usage site in the watchdog code.
Thanks,
tglx
next prev parent reply other threads:[~2024-02-20 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:19 [PATCHv8 0/2] *** Detect interrupt storm in softlockup *** Bitao Hu
2024-02-19 16:19 ` [PATCHv8 1/2] watchdog/softlockup: low-overhead detection of interrupt Bitao Hu
2024-02-19 16:19 ` [PATCHv8 2/2] watchdog/softlockup: report the most frequent interrupts Bitao Hu
2024-02-20 9:35 ` Thomas Gleixner [this message]
2024-02-20 9:49 ` 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=87le7fiiku.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=dianders@chromium.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=kernelfans@gmail.com \
--cc=kvm@vger.kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox