From: Muni Sekhar <munisekharrms@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: interrupt latency
Date: Mon, 29 Jul 2019 23:16:52 +0530 [thread overview]
Message-ID: <CAHhAz+j6Em-JqLRa80Qp81jtB_Jb+11A0uR+TdLMOPuW5ZM5Aw@mail.gmail.com> (raw)
Hi All,
I used the Linux kernel’s ‘Ftrace’ framework for tracing the interrupt
latencies.
Sometimes I noticed a delay(time between do_IRQ() to start of ISR())
in start of ISR(interrupt service routine) to execute , some other
times I noticed ISR execution time(entering and exiting a function) is
very high.
I’d like to know in which scenarios, ISR gets executed lately?
In which scenarios, ISR execution time is very high?
Can someone please clarify me on this.
--
Thanks,
Sekhar
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2019-07-29 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHhAz+j6Em-JqLRa80Qp81jtB_Jb+11A0uR+TdLMOPuW5ZM5Aw@mail.gmail.com \
--to=munisekharrms@gmail.com \
--cc=kernelnewbies@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).