---
name: "trace_irq_handler_exit"
section: "9"
platform: "linux"
package: "linux-manual-4.9"
version: "4.9.228-1"
release: "Debian 9 (Stretch)"
platforms: ["linux"]
url: "https://new.carta.tech/trace_irq_handler_exit"
---

# trace\_irq\_handler\_exit(9)

called immediately after the irq action handler returns

## NAME

trace\_irq\_handler\_exit - called immediately after the irq action handler returns

## SYNOPSIS

**void trace\_irq\_handler\_exit(int** *irq***, struct irqaction \*** *action***, int** *ret***);**

## ARGUMENTS

*irq*

irq number

*action*

pointer to struct irqaction

*ret*

return value

## DESCRIPTION

If the *ret* value is set to IRQ\_HANDLED, then we know that the corresponding *action*-\>handler successfully handled this irq. Otherwise, the irq might be a shared irq line, or the irq was not handled successfully. Can be used in conjunction with the irq\_handler\_entry to understand irq handler latencies.

## AUTHORS

**Jason Baron** \<jbaron@redhat.com\>

Author.

**William Cohen** \<wcohen@redhat.com\>

Author.

## COPYRIGHT