From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "e- d8 i> sunshilong" <sunshilong369@gmail.com>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>
Subject: Re: Why are there "<IRQ>" and "</IRQ>" in the call trace section? What does them imply?
Date: Fri, 10 Jul 2020 21:05:20 -0400 [thread overview]
Message-ID: <206158.1594429520@turing-police> (raw)
In-Reply-To: <CAAvDm6bRTfHzWysY0=pw7beB6GmXY7PN0h-xv7HMGDY3VACNcA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]
On Fri, 10 Jul 2020 13:29:29 +0800, "e- d8 i> sunshilong" said:
> [72873.713473] <IRQ>
> [72873.713474] switch_mm_irqs_off+0x31b/0x4e0
> [72873.713475] xnarch_switch_to+0x2f/0x80
> [72873.713476] ___xnsched_run.part.74+0x154/0x480
> [72873.713476] ___xnsched_run+0x35/0x50
> [72873.713477] xnintr_irq_handler+0x346/0x4c0
> [72873.713478] ? xnintr_core_clock_handler+0x1b6/0x360
> [72873.713479] dispatch_irq_head+0x8e/0x110
> [72873.713479] ? xnintr_irq_handler+0x5/0x4c0
> [72873.713481] ? dispatch_irq_head+0x8e/0x110
> [72873.713482] __ipipe_dispatch_irq+0xd9/0x1c0
> [72873.713483] __ipipe_handle_irq+0x86/0x1e0
> [72873.713483] common_interrupt+0xf/0x2c
> [72873.713484] </IRQ>
>
> Maybe, the later one(i.e. </IRQ>) implies there was an interrupt
> request and the common_interuppt() function handler it.
No. It's possible for the kernel traceback to include some routines that
were in an IRQ, and some more that were outside IRQ context. So you
can tell which are which, the stack dump is formatted as:
<IRQ>
function that was running when the trace was called for
the function that call it
another function back
(...)
interrupt_handler of some sort
</IRQ>
function that was running when the interrupt hit
this caller
and its parent
etc
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-07-11 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 5:29 Why are there "<IRQ>" and "</IRQ>" in the call trace section? What does them imply? 孙世龙 sunshilong
2020-07-11 1:05 ` Valdis Klētnieks [this message]
2020-07-12 10:15 ` CVS
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=206158.1594429520@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=sunshilong369@gmail.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).