Re: [ARM64] Printing IRQ stack usage information

From: valdis.kletnieks@vt.edu
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: mark.rutland@arm.com, jungseoklee85@gmail.com,
	kernelnewbies@kernelnewbies.org, catalin.marinas@arm.com,
	barami97@gmail.com, will.deacon@arm.com,
	open list <linux-kernel@vger.kernel.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	takahiro.akashi@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [ARM64] Printing IRQ stack usage information
Date: Thu, 15 Nov 2018 11:49:09 -0500	[thread overview]
Message-ID: <28496.1542300549@turing-police.cc.vt.edu> (raw)
Message-ID: <20181115164909.j14BP_5ucykIl_REeWHeQDj94CLz6CqCoZPNF21xWuo@z> (raw)
In-Reply-To: <CAOuPNLiLj9be5iUdpUiLqiTge-xYY_v4_VLs-ah2_PygG7vxdg@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 1149 bytes --]

On Thu, 15 Nov 2018 18:52:39 +0530, Pintu Agarwal said:

> Currently, when I tested this (as a proc interface), I got the below output:
> CPU    UNUSED-STACK    ACTUAL-STACK
>  0         16368                     16384

> 3) How should I test it to get the different usage values for unused stack ?
>     Can I get these values by implementing a sample interrupt handler,
> and printing information from there?

Hint 1:  If you're in a state where seq_printf() is legal, how many IRQ's are
on this processor's IRQ stack?

Hint 2:  What are the chances that some other CPU is currently in an IRQ?
(run 'top' and look for what percent of time that's happening)

Hint 3: what are the chances that the value of irq_stack_ptr is already stale
by the time seq_printf() finishes running?

Hint 4: what happens to the validity of your output if you get rescheduled
in the middle of that for_each loop?

(In other words, this code is terribly racy and is probably not going to answer
whatever debugging question you were working on..  If your question is "Did one
of the CPUs blow out its IRQ stack (or come close to doing so)?" there's better
approaches.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 486 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies