From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [ARM64] Printing IRQ stack usage information
Date: Fri, 16 Nov 2018 06:33:08 -0500 [thread overview]
Message-ID: <49219.1542367988@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAOuPNLj8wj=tPJo8L3oS7o8iTQcyhZ0W-GH6xmP_GsG4r7YdAQ@mail.gmail.com>
On Fri, 16 Nov 2018 11:44:36 +0530, Pintu Agarwal said:
> > If your question is "Did one
> > of the CPUs blow out its IRQ stack (or come close to doing so)?" there's better
> > approaches.
> >
> Yes, exactly, this is what the main intention.
> If you have any better idea about this approach, please refer me.
> It will be of great help.
Look at the code controlled by '#ifdef CONFIG_DEBUG_STACK_USAGE'
which does the same thing for process stacks, or CONFIG_SCHED_STACK_END_CHECK
or the use of guard pages for detecting stack overrun....
WARNING: multiple messages have this Message-ID (diff)
From: valdis.kletnieks@vt.edu
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: mark.rutland@arm.com, Jungseok Lee <jungseoklee85@gmail.com>,
kernelnewbies@kernelnewbies.org, catalin.marinas@arm.com,
Sungjinn Chung <barami97@gmail.com>,
will.deacon@arm.com, open list <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [ARM64] Printing IRQ stack usage information
Date: Fri, 16 Nov 2018 06:33:08 -0500 [thread overview]
Message-ID: <49219.1542367988@turing-police.cc.vt.edu> (raw)
Message-ID: <20181116113308.GaadVmzd77wlogiovoZnaC1qe-PT_J699jYDUdtY-kM@z> (raw)
In-Reply-To: <CAOuPNLj8wj=tPJo8L3oS7o8iTQcyhZ0W-GH6xmP_GsG4r7YdAQ@mail.gmail.com>
On Fri, 16 Nov 2018 11:44:36 +0530, Pintu Agarwal said:
> > If your question is "Did one
> > of the CPUs blow out its IRQ stack (or come close to doing so)?" there's better
> > approaches.
> >
> Yes, exactly, this is what the main intention.
> If you have any better idea about this approach, please refer me.
> It will be of great help.
Look at the code controlled by '#ifdef CONFIG_DEBUG_STACK_USAGE'
which does the same thing for process stacks, or CONFIG_SCHED_STACK_END_CHECK
or the use of guard pages for detecting stack overrun....
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-16 11:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 13:22 [ARM64] Printing IRQ stack usage information Pintu Agarwal
2018-11-15 13:22 ` Pintu Agarwal
2018-11-15 16:49 ` valdis.kletnieks at vt.edu
2018-11-15 16:49 ` valdis.kletnieks
2018-11-16 6:14 ` Pintu Agarwal
2018-11-16 6:14 ` Pintu Agarwal
2018-11-16 11:33 ` valdis.kletnieks at vt.edu [this message]
2018-11-16 11:33 ` valdis.kletnieks
2018-11-16 14:40 ` Pintu Agarwal
2018-11-16 14:40 ` Pintu Agarwal
2018-11-16 16:46 ` valdis.kletnieks at vt.edu
2018-11-16 16:46 ` valdis.kletnieks
2018-11-16 17:43 ` Pintu Agarwal
2018-11-16 17:43 ` Pintu Agarwal
2018-11-16 18:31 ` valdis.kletnieks at vt.edu
2018-11-16 18:31 ` valdis.kletnieks
2018-11-17 13:06 ` Pintu Agarwal
2018-11-17 13:06 ` Pintu Agarwal
2018-11-20 12:51 ` Pintu Agarwal
2018-11-20 12:51 ` Pintu Agarwal
2018-11-20 19:03 ` valdis.kletnieks at vt.edu
2018-11-20 19:03 ` valdis.kletnieks
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=49219.1542367988@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).