From: Pintu Agarwal <pintu.ping@gmail.com>
To: open list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Russell King - ARM Linux <linux@armlinux.org.uk>,
kernelnewbies@kernelnewbies.org,
Pintu Kumar <pintu.ping@gmail.com>,
jungseoklee85@gmail.com, catalin.marinas@arm.com,
will.deacon@arm.com, takahiro.akashi@linaro.org,
mark.rutland@arm.com, barami97@gmail.com
Subject: [ARM64] Printing IRQ stack usage information
Date: Thu, 15 Nov 2018 18:52:39 +0530 [thread overview]
Message-ID: <CAOuPNLiLj9be5iUdpUiLqiTge-xYY_v4_VLs-ah2_PygG7vxdg@mail.gmail.com> (raw)
Message-ID: <20181115132239.x7AYCdTLDP5ey72A9oKyPGNCf_wQBxPmheBsfKpcW6A@z> (raw)
Hi All,
I have a requirement in printing irq stack usage information for each cpu.
I am using the following:
Linux Kernel: 4.9.x
Board: hikey620 (arm64, armv8 with 8 cores)
Platform: Ubuntu 14 debian
As a vague idea, I tried to implement like this:
-------------------------------------------------------------
static int dump_irq_stack_info(void)
{
int cpu, actual;
unsigned long irq_stack_ptr;
//unsigned long sp, sp1;
unsigned long stack_start;
unsigned long used;
actual = IRQ_STACK_SIZE;
used = 0;
pr_info("CPU UNUSED-STACK ACTUAL-STACK\n");
//seq_printf(m, "CPU UNUSED-STACK ACTUAL-STACK\n");
for_each_present_cpu(cpu) {
irq_stack_ptr = IRQ_STACK_PTR(cpu);
//sp1 = current_stack_pointer;
//sp = IRQ_STACK_TO_TASK_STACK(irq_stack_ptr);
stack_start = (unsigned long)per_cpu(irq_stack, cpu);
used = irq_stack_ptr - stack_start;
pr_info("%2d %10lu %10d\n", cpu, used, actual);
//seq_printf(m, "%2d %10lu %10d\n", cpu, used, actual);
}
return 0;
}
-------------------------------------------------------------
Currently, when I tested this (as a proc interface), I got the below output:
CPU UNUSED-STACK ACTUAL-STACK
0 16368 16384
1 16368 16384
2 16368 16384
3 16368 16384
4 16368 16384
5 16368 16384
6 16368 16384
7 16368 16384
-------------------------------------------------------------
But, I have some doubts:
1) I am not sure if my implementation is in right direction, or the
logic is totally wrong.
2) Is there better way to perform the similar objective?
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?
If this works, then I want to use it as part of dump_backtrace() function.
If anybody have done a similar thing in past, or have some ideas to
share, please help me.
Note: This is required only for our internal debugging purpose.
Regards,
Pintu
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2018-11-15 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 13:22 Pintu Agarwal [this message]
2018-11-15 13:22 ` [ARM64] Printing IRQ stack usage information 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
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=CAOuPNLiLj9be5iUdpUiLqiTge-xYY_v4_VLs-ah2_PygG7vxdg@mail.gmail.com \
--to=pintu.ping@gmail.com \
--cc=barami97@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=jungseoklee85@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).