From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
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, 6 Aug 2010 13:46:11 +0200 [thread overview]
Message-ID: <20100806114611.GE1981@jolsa.brq.redhat.com> (raw)
In-Reply-To: <87bp9gc783.fsf@basil.nowhere.org>
On Fri, Aug 06, 2010 at 01:26:36PM +0200, Andi Kleen wrote:
> 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?
As I was asked to do that for other guys, I'm not completely sure.
Anyway the reason I got was, that while debuging crash it seemed
some IPIs might got lost.
Also it'd be probably used as a tracepoint itself via additional code,
than by ring buffer tracing.
I'll check if I can get more justifing info..
jirka
>
> -Andi
> --
> ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-08-06 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:09 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 ` [RFC 0/2] apic: tracing IPI events Andi Kleen
2010-08-06 11:46 ` Jiri Olsa [this message]
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=20100806114611.GE1981@jolsa.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=andi@firstfloor.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®