From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 00/11] Text Edit Lock for 2.6.24-rc4-git3
Date: Thu, 6 Dec 2007 09:07:22 -0500 [thread overview]
Message-ID: <20071206140722.GA10542@Krystal> (raw)
In-Reply-To: <20071206094712.GB10455@osiris.boeblingen.de.ibm.com>
* Heiko Carstens (heiko.carstens@de.ibm.com) wrote:
> On Wed, Dec 05, 2007 at 09:02:46PM -0500, Mathieu Desnoyers wrote:
> > Hi,
> >
> > Here is a repost of the text edit lock for 2.6.24-rc4-mm3. It is useful to
> > coordinate modification of live kernel code patching.
> >
> > It includes a modification to kprobes (its first user) and is useful for the
> > Immediate Values.
> >
> > It could be interesting to queue it for 2.6.25.
>
> Everytime I see your huge patchset I'm wondering what it is good for and
> give up since the patch set is large. It would be very helpful if your
> patch descriptions would not only describe what you do but also why you
> do it.
Kernel tracing, so that we can help userspace application developpers
and kernel developpers debug problems caused by system-wide
program interactions.
See :
The patchset, including the LTTng tracer :
http://ltt.polymtl.ca/lttng/patch-2.6.24-rc4-git3-lttng-0.10-pre39.tar.bz2
To get the userspace apps that are needed to do something useful :
http://ltt.polymtl.ca/lttng/ltt-control-0.46-06112007.tar.gz
http://ltt.polymtl.ca/packages/lttv-0.10.0-pre5-05122007.tar.gz
http://ltt.polymtl.ca/svn/ltt/branches/poly/QUICKSTART
(a bit outdated)
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2007-12-06 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 2:02 [patch 00/11] Text Edit Lock for 2.6.24-rc4-git3 Mathieu Desnoyers
2007-12-06 2:02 ` [patch 01/11] Kprobes - use a mutex to protect the instruction pages list Mathieu Desnoyers
2007-12-06 2:02 ` [patch 02/11] Kprobes - do not use kprobes mutex in arch code Mathieu Desnoyers
2007-12-06 2:02 ` [patch 03/11] Kprobes - declare kprobe_mutex static Mathieu Desnoyers
2007-12-06 2:02 ` [patch 04/11] Add INIT_ARRAY() to kernel.h Mathieu Desnoyers
2007-12-06 2:02 ` [patch 05/11] Text Edit Lock - Architecture Independent Code Mathieu Desnoyers
2007-12-06 2:02 ` [patch 06/11] Text Edit Lock - Alternative code for x86 Mathieu Desnoyers
2007-12-06 12:19 ` pageexec
2007-12-06 14:21 ` Mathieu Desnoyers
2007-12-06 14:44 ` Mathieu Desnoyers
2007-12-06 13:58 ` pageexec
2007-12-06 15:17 ` [patch 06/11] Text Edit Lock - Alternative code for x86 (update) Mathieu Desnoyers
2007-12-06 2:02 ` [patch 07/11] Text Edit Lock - kprobes architecture independent support Mathieu Desnoyers
2007-12-06 2:02 ` [patch 08/11] Text Edit Lock - kprobes x86_32 Mathieu Desnoyers
2007-12-06 2:02 ` [patch 09/11] Text Edit Lock - kprobes x86_64 Mathieu Desnoyers
2007-12-06 2:02 ` [patch 10/11] Text Edit Lock - x86_32 standardize debug rodata Mathieu Desnoyers
2007-12-06 2:02 ` [patch 11/11] Text Edit Lock - x86_64 " Mathieu Desnoyers
2007-12-06 9:47 ` [patch 00/11] Text Edit Lock for 2.6.24-rc4-git3 Heiko Carstens
2007-12-06 14:07 ` Mathieu Desnoyers [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=20071206140722.GA10542@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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