[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1904052314410.1802@nanos.tec.linutronix.de>
Date: Fri, 5 Apr 2019 23:15:34 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Daniel Bristot de Oliveira <bristot@...hat.com>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Andy Lutomirski <luto@...nel.org>,
Clark Williams <williams@...hat.com>, x86@...nel.org
Subject: Re: [PATCH V2 1/2] trace,x86: Add external_interrupts to the
irq_vectors class
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,
tglx
Powered by blists - more mailing lists