Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:kernel\irq\debug.h Create Date:2022-07-28 10:08:06
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:print_irq_desc

Proto:static inline void print_irq_desc(unsigned int irq, struct irq_desc *desc)

Type:void

Parameter:

TypeParameterName
unsigned intirq
struct irq_desc *desc
13  DEFINE_RATELIMIT_STATE(ratelimit, 5 * HZ, 5)
15  If Not __ratelimit( & ratelimit) Then Return
18  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
20  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
22  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
24  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
25  If IRQ action list Then
26  printk - print a kernel message*@fmt: format string* This is printk(). It can be called from any context. We want it to work.* We try to grab the console_lock. If we succeed, it's easy - we log the* output and call the console drivers
42  FIXME (IRQS_INPROGRESS)
43  FIXME (IRQS_DISABLED)
44  FIXME (IRQS_MASKED)
Caller
NameDescribe
handle_bad_irqhandle_bad_irq - handle spurious and unhandled irqs*@desc: description of the interrupt* Handles spurious and unhandled IRQ's. It also prints a debugmessage.
ack_badWhat should we do if we get a hw irq event on an illegal vector?* Each architecture has to answer this themself.