From: Thomas Gleixner <tglx@linutronix.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Bitao Hu <yaoma@linux.alibaba.com>,
akpm@linux-foundation.org, pmladek@suse.com, maz@kernel.org,
liusong@linux.alibaba.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] watchdog/softlockup: report the most time-consuming hardirq
Date: Thu, 15 Feb 2024 02:02:45 +0100 [thread overview]
Message-ID: <87wmr6edze.ffs@tglx> (raw)
In-Reply-To: <CAD=FV=URLh5N6smwdnPXn6di8iek_vn=uBYFWBpCdsuRjLK8ew@mail.gmail.com>
On Wed, Feb 14 2024 at 15:39, Doug Anderson wrote:
> On Wed, Feb 14, 2024 at 3:36 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>> On Tue, Jan 23 2024 at 20:12, Bitao Hu wrote:
>> As a side note: While C does not allow proper encapsulation it's a non
>> starter to fiddle with the interrupt descriptor internals in random code
>> just because the compiler allows you to do so. While not enforced there
>> are clear boundaries and we went a long way to encapsulate this.
>
> I think you must have gotten dropped from all the future versions of
> this patch series when Bitao took my advice and started using
> interrupt counts instead of tracing. For what it's worth, the latest
> version can be found at:
>
> https://lore.kernel.org/r/20240214021430.87471-1-yaoma@linux.alibaba.com
Yes. I'm not on CC and for some stupid reason it evaded my LKML filters.
Let me find that thread and stare at it.
Thanks,
tglx
next prev parent reply other threads:[~2024-02-15 1:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 12:12 [PATCH 0/3] *** Detect interrupt storm in softlockup *** Bitao Hu
2024-01-23 12:12 ` [PATCH 1/3] watchdog/softlockup: low-overhead detection of interrupt storm Bitao Hu
2024-01-24 1:43 ` Liu Song
2024-01-24 2:48 ` yaoma
2024-01-25 0:19 ` Doug Anderson
2024-01-25 8:31 ` Bitao Hu
2024-01-25 15:08 ` Doug Anderson
2024-01-26 5:25 ` kernel test robot
2024-01-23 12:12 ` [PATCH 2/3] watchdog/softlockup: report the most time-consuming hardirq Bitao Hu
2024-01-25 0:19 ` Doug Anderson
2024-01-25 7:50 ` Bitao Hu
2024-01-25 9:19 ` Bitao Hu
2024-02-14 23:36 ` Thomas Gleixner
2024-02-14 23:39 ` Doug Anderson
2024-02-15 1:02 ` Thomas Gleixner [this message]
2024-01-23 12:12 ` [PATCH 3/3] watchdog/softlockup: add parameter to control the reporting of " Bitao Hu
2024-01-26 5:25 ` kernel test robot
2024-01-26 6:07 ` kernel test robot
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=87wmr6edze.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=maz@kernel.org \
--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