From: fche@redhat.com (Frank Ch. Eigler)
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
akpm@linux-foundation.org, Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, ltt-dev@lists.casi.polymtl.ca
Subject: Re: LTTng finds abnormally long APIC interrupt handler : 58.2 ms
Date: Thu, 07 Aug 2008 14:15:57 -0400 [thread overview]
Message-ID: <y0mwsisitcy.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0808071314320.20931@gandalf.stny.rr.com> (Steven Rostedt's message of "Thu, 7 Aug 2008 13:41:09 -0400 (EDT)")
Steven Rostedt <rostedt@goodmis.org> writes:
> [...]
>> It all holds in a small module. Having the ability to connect any marker
>> on any generic probe from the lttng marker interface has been very
>> useful to do all this. Actually, this module has to be built into the
>> kernel because ftrace does not permit breeing the trace_ops data
>> structure. :/
>
> I did this purposely. The reason is that there is no safe way to release
> the trace_ops, because you never know if something is in the function
> you pointed to. If you remove the module after that, it crashes.
>
> I've been thinking of exporting it, and make it so that once you
> register something to the trace_ops, I'll up the module count, and never
> let that module unload.
This issue will need some sort of resolution if systemtap is to be
able to hook up to ftrace. Perhaps we could have a second/nested API
that suffers the costs of explicit reference counting, but does permit
dynamic attach and robust detach.
- FChE
next prev parent reply other threads:[~2008-08-07 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 18:20 LTTng finds abnormally long APIC interrupt handler : 58.2 ms Mathieu Desnoyers
2008-08-05 19:24 ` Steven Rostedt
2008-08-07 16:09 ` Mathieu Desnoyers
2008-08-07 17:41 ` Steven Rostedt
2008-08-07 18:15 ` Frank Ch. Eigler [this message]
2008-08-07 18:24 ` Mathieu Desnoyers
2008-08-07 18:32 ` Steven Rostedt
2008-08-08 23:11 ` Mathieu Desnoyers
2008-08-09 7:14 ` Peter Zijlstra
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=y0mwsisitcy.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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