From: Andi Kleen <andi@firstfloor.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: mingo@elte.hu, rostedt@goodmis.org, yhlu.kernel@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/2] apic: tracing IPI events
Date: Fri, 06 Aug 2010 13:26:36 +0200 [thread overview]
Message-ID: <87bp9gc783.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1281006578-5073-1-git-send-email-jolsa@redhat.com> (Jiri Olsa's message of "Thu, 5 Aug 2010 13:09:36 +0200")
Jiri Olsa <jolsa@redhat.com> writes:
>
> please let me know what you think
You forgot to state why you want it?
In generall the only case that should happen anytime commonly is mask,
the others only for obscure uncommon paths.
However there is already accounting for it in /proc/interrupts
that can be easily sampled. Does adding additional tracing really give
any value?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-08-06 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:09 [RFC 0/2] apic: tracing IPI events Jiri Olsa
2010-08-05 11:09 ` [PATCH 1/2] apic: adding apic_send_IPI_* methods for apic's IPI callbacks Jiri Olsa
2010-08-05 11:09 ` [PATCH 2/2] apic,trace: IPI sent trace event Jiri Olsa
2010-08-06 11:26 ` Andi Kleen [this message]
2010-08-06 11:46 ` [RFC 0/2] apic: tracing IPI events Jiri Olsa
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=87bp9gc783.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=yhlu.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.