From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Lutomirski <luto@kernel.org>,
Clark Williams <williams@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH V2 1/2] trace,x86: Add external_interrupts to the irq_vectors class
Date: Fri, 5 Apr 2019 23:15:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904052314410.1802@nanos.tec.linutronix.de> (raw)
In-Reply-To: <833f2a192b491649e4d46cec51028d07c96bbf5e.1554142415.git.bristot@redhat.com>
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
next prev parent reply other threads:[~2019-04-05 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:19 [PATCH V2 1/2] trace,x86: Add external_interrupts to the irq_vectors class Daniel Bristot de Oliveira
2019-04-01 18:19 ` [PATCH V2 2/2] trace,x86: Add nmi " Daniel Bristot de Oliveira
2019-04-05 21:50 ` Thomas Gleixner
2019-04-08 12:24 ` Daniel Bristot de Oliveira
2019-04-08 13:46 ` Steven Rostedt
2019-04-08 13:57 ` Daniel Bristot de Oliveira
2019-04-08 14:25 ` Steven Rostedt
2019-04-05 21:15 ` Thomas Gleixner [this message]
2019-04-08 9:48 ` [PATCH V2 1/2] trace,x86: Add external_interrupts " Daniel Bristot de Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1904052314410.1802@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=williams@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).