linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishnu Motghare <vishnumotghare@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to print stack uses of IRQ in ARM64
Date: Thu, 31 May 2018 15:37:18 +0530	[thread overview]
Message-ID: <CADSz7_dsv91M4tsuxpxtA+_gdX34gYes6u8UnbGz9Jzgit2zqA@mail.gmail.com> (raw)

I found this discussion (https://lwn.net/Articles/657969/) regarding
implementation of separate IRQ stack for  ARM64.

My understanding is each CPU  getting its own IRQ stack. So is it
possible to print the stack uses of each IRQ handler? like, How much
stack is used & how much left free ?

like in process context we have API like stack_not_used(struct
task_struct *p) to get the unused stack  of processes. So, is it
possible to get the similar result for IRQ?

             reply	other threads:[~2018-05-31 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 10:07 Vishnu Motghare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-31 10:01 How to print stack uses of IRQ in ARM64 Vishnu Motghare
2018-06-05 13:12 ` Andy Shevchenko
2018-06-05 17:40   ` James Morse

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=CADSz7_dsv91M4tsuxpxtA+_gdX34gYes6u8UnbGz9Jzgit2zqA@mail.gmail.com \
    --to=vishnumotghare@gmail.com \
    --cc=linux-kernel@vger.kernel.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).