---
name: "trace_irq_handler_entry"
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_entry"
---

# trace\_irq\_handler\_entry(9)

called immediately before the irq action handler

## NAME

trace\_irq\_handler\_entry - called immediately before the irq action handler

## SYNOPSIS

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

## ARGUMENTS

*irq*

irq number

*action*

pointer to struct irqaction

## DESCRIPTION

The struct irqaction pointed to by *action* contains various information about the handler, including the device name, *action*-\>name, and the device id, *action*-\>dev\_id. When used in conjunction with the irq\_handler\_exit tracepoint, we can figure out irq handler latencies.

## AUTHORS

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

Author.

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

Author.

## COPYRIGHT