From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/6] Linux Kernel Markers
Date: Wed, 30 May 2007 08:16:18 -0400 [thread overview]
Message-ID: <20070530121618.GD22567@Krystal> (raw)
In-Reply-To: <20070529183725.179570071@polymtl.ca>
Same here : it applies at the end of 2.6.21-mm2, not 2.6.22-mm1 as said
in my message.
* Mathieu Desnoyers (mathieu.desnoyers@polymtl.ca) wrote:
> Hi,
>
> The Linux Kernel Markers have been reworked to now depend on the "Conditional
> Calls" as a basic infrastructure for enabling the calls to the function
> pointers (probes).
>
> The second major change in this release is the use of a hash table to keep track
> of the enabled markers : it permits it issue the marker_arm_probe before loading
> a module containing the specified probe. The probe connexion to the marker is
> done both when the marker is armed and at module load time. It fixes an
> unexpected behavior of the previous version, which was due to the fact that
> users might have expected that the markers would be set for newly loaded
> modules. Since there is no dependency between the marker and modules, the order
> could easily be wrong.
>
> A hash table using a hash of the marker name is used to give O(1) lookup at
> module load time.
>
> This serie of patches depends on the conditional calls. Please add at the end of
> the 2.6.22-mm1 series:
>
> use-extra_rwdata-in-architectures.patch
> #
> linux-kernel-markers-architecture-independent-code.patch
> linux-kernel-markers-hash-table.patch
> linux-kernel-markers-kconfig-menus.patch
> linux-kernel-markers-documentation.patch
> linux-kernel-markers-port-blktrace-to-markers.patch
>
> 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
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
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-05-30 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:37 [patch 0/6] Linux Kernel Markers Mathieu Desnoyers
2007-05-29 18:37 ` [patch 1/6] Use EXTRA_RWDATA in architectures Mathieu Desnoyers
2007-05-29 18:37 ` Mathieu Desnoyers
2007-05-29 18:54 ` Sam Ravnborg
2007-05-30 13:06 ` Mathieu Desnoyers
2007-05-29 18:37 ` [patch 2/6] Linux Kernel Markers, architecture independent code Mathieu Desnoyers
2007-05-29 18:37 ` [patch 3/6] Linux Kernel Markers - Hash Table Mathieu Desnoyers
2007-05-29 18:37 ` [patch 4/6] Linux Kernel Markers - Add kconfig menus for the marker code Mathieu Desnoyers
2007-05-29 18:37 ` [patch 5/6] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-05-29 18:37 ` [patch 6/6] Port of blktrace to the Linux Kernel Markers Mathieu Desnoyers
2007-05-30 12:16 ` 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=20070530121618.GD22567@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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.