* How to debug when IRQs are disabled for few milliseconds?
@ 2017-11-22 13:19 priyaranjan
0 siblings, 0 replies; only message in thread
From: priyaranjan @ 2017-11-22 13:19 UTC (permalink / raw)
To: kernelnewbies
Hello All,
I'm having issues on DRA7x based Android system. We have seen that
that when we use 'cat' command in shell to dump some debug trace
the 'shell' get scheduled in CPU0 and sometimes in CPU1. IRQs get
blocked in the system for the amount of time the Shell runs. We have
captured systrace which shows the same. Since we have some stringent
requirement to service the IRQs within 2 miliisecond
approx, we are missing the IRQs for important peripherals like Audio.
I have tried the Hard lockup but the threshold can be programmed
minimum to 1second hence could not succeed in this.
I have also tried to use ftrace, however it was very difficult to find
out where exactly the IRQs are getting disabled.
Can anyone help?
Regards,
Priyaranjan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-11-22 13:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-22 13:19 How to debug when IRQs are disabled for few milliseconds? priyaranjan
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).