On 4/5/19 11:15 PM, Thomas Gleixner wrote:
> On Mon, 1 Apr 2019, Daniel Bristot de Oliveira wrote:
>
>> Currently, the irq_vectors is showing the entry and exit events for
>> the interrupts of the architecture, but not for external interrupts.
>
> Those are covered by the irq tracepoints. Is
On Mon, 1 Apr 2019, Daniel Bristot de Oliveira wrote:
> Currently, the irq_vectors is showing the entry and exit events for
> the interrupts of the architecture, but not for external interrupts.
Those are covered by the irq tracepoints. Is there a really good reason why
we need both?
Thanks,
Currently, the irq_vectors is showing the entry and exit events for
the interrupts of the architecture, but not for external interrupts.
Adds the tracepoints for external interrupts.
Example of output:
-0 [000] d.h. 102.890935: external_interrupt_entry: vector=35
-0 [000] d.h.
3 matches
Mail list logo