[PATCH 16/30] x86, kaiser: map trace interrupt entry

From: Dave Hansen All of the interrupt entry/exit code is in a special section (.irqentry.text). This enables the ftrace code to figure out when the kernel is executing in the "grey area" of interrupt handling before the C code has taken over and marked the data

[PATCH 16/30] x86, kaiser: map trace interrupt entry

From: Dave Hansen All of the interrupt entry/exit code is in a special section (.irqentry.text). This enables the ftrace code to figure out when the kernel is executing in the "grey area" of interrupt handling before the C code has taken over and marked the data structures indicating that an

[PATCH 16/30] x86, kaiser: map trace interrupt entry

From: Dave Hansen We put all of the interrupt entry/exit code into a special section (.irqentry.text). This enables the ftrace code to figure out when we are in a "grey area" of interrupt handling before the C code has taken over and marked the data structures that

[PATCH 16/30] x86, kaiser: map trace interrupt entry

From: Dave Hansen We put all of the interrupt entry/exit code into a special section (.irqentry.text). This enables the ftrace code to figure out when we are in a "grey area" of interrupt handling before the C code has taken over and marked the data structures that we are in an interrupt.