From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <zanussi@us.ibm.com>,
Karim Yaghmour <karim@opersys.com>,
Paul Mundt <lethal@linux-sh.org>, Jes Sorensen <jes@sgi.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
Douglas Niehaus <niehaus@eecs.ku.edu>,
ltt-dev@shafik.org, systemtap@sources.redhat.com
Subject: [PATCH] LTTng 0.6.36 for 2.6.18 (now with markers)
Date: Fri, 24 Nov 2006 22:06:00 -0000 [thread overview]
Message-ID: <20061124214831.GA25048@Krystal> (raw)
Hi,
I have, since a few weeks, moved LTTng to the markers infrastructure. I
left the ltt-dev users and contributors test the markers and LTTng on various
architectures (i386, x86_64, PowerPC, -ppc, ARM, MIPS) before posting it on
LKML.
The most important new features since the my post :
- Use DebugFS
- Use the "Markers" infrastructure (updated since the last post on LKML).
- Dynamically loadable "probes" that connects to the markers.
- CPU Hotplug support (this piece seemed necessary for the Xen port I am
currently working on)
- Use of per-CPU atomic operations even on SMP machines (no lock prefix, no
memory barriers) to update the per-cpu counters. An explicit smp_wmb()
is used at the one place where the subbuffers are tagged "full" and
smp_rmb() is used in the buffer consumer just after it reads this counter
indicating that the subbuffer is full.
I am not submitting the probes themselves, as they can be provided as separate
kernel modules.
Comments and constructive criticism are, as always, welcome.
The patches follow.
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2006-11-24 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 22:06 Mathieu Desnoyers [this message]
2006-11-27 16:57 ` Christoph Hellwig
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=20061124214831.GA25048@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=niehaus@eecs.ku.edu \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=zanussi@us.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).