Re: [patch 1/4] Linux Kernel Markers - Architecture Independent Code

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Mathieu Desnoyers <mathieu.desnoyers@...>
Cc: Denys Vlasenko <vda.linux@...>, <systemtap@...>, Christoph Hellwig <hch@...>, Rusty Russell <rusty@...>, <akpm@...>, <linux-kernel@...>
Date: Monday, October 15, 2007 - 3:41 pm

Hi -

I wrote:


Our team is farther along adapting to this change against 2.6.23-mm1,
and we have run into a complication.  It's more of a distribution
issue.

We would prefer to retain systemtap's capability to build
instrumentation for a kernel other than the currently running one.
Such instrumentation can be then copied and run on a distinct machine.
This has meant relying on development data: make install_headers +
Makefiles (as packaged by Fedora/RHEL), and to a lesser extent
separated debugging information.

Markers are attractive partly because they don't require debugging
information, so the data needs to be found in an executable image.
But we prefer not to force the executable image itself to be
installed, for example because /boot is relatively small.  So we would
prefer something in between: something small that we can put into the
development package.

If there exists sympathy to this problem, Roland McGrath supposes we
could implement a standardized solution, a file like Module.symvers,
containing the marker names & format strings extracted at build time.
Any opinions?


PS. I wonder why the marker name/format strings are put into a
__markers_strings object section at all, considering that the only
place where that is used again appears to be this code in
kernel/module.c:

        markersstringsindex = find_sec(hdr, sechdrs, secstrings,
                                        "__markers_strings");

and the "markersstringsindex" variable is never used.


- FChE
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 1/4] Linux Kernel Markers - Architecture Independent ..., Mathieu Desnoyers, (Tue Sep 18, 5:13 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Fri Sep 21, 9:45 am)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Wed Sep 19, 7:37 am)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Fri Sep 21, 8:58 am)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Fri Sep 21, 9:38 am)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Frank Ch. Eigler, (Mon Oct 15, 3:41 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Mon Oct 15, 7:12 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Thu Oct 25, 3:17 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Frank Ch. Eigler, (Fri Oct 26, 10:28 am)
[PATCH] markers: modpost, Roland McGrath, (Wed Oct 31, 9:06 pm)
Re: [PATCH] markers: modpost, Mathieu Desnoyers, (Wed Oct 31, 10:46 pm)
Re: [PATCH] markers: modpost, Roland McGrath, (Thu Nov 1, 5:37 am)
Re: [PATCH] markers: modpost, Mathieu Desnoyers, (Thu Nov 1, 7:24 am)
Re: [PATCH] markers: modpost, David Smith, (Thu Nov 8, 3:31 pm)
Re: [PATCH] markers: modpost, Mathieu Desnoyers, (Thu Nov 8, 3:36 pm)
Re: [PATCH] markers: modpost, David Smith, (Fri Nov 9, 12:36 pm)
Re: [PATCH] markers: modpost, Mathieu Desnoyers, (Sun Nov 11, 7:24 pm)
Re: [PATCH] markers: modpost, David Smith, (Thu Nov 8, 3:45 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Christoph Hellwig, (Fri Sep 21, 9:07 am)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Wed Sep 19, 2:46 pm)
Re: [patch 1/4] Linux Kernel Markers - Architecture Independ..., Mathieu Desnoyers, (Wed Sep 19, 2:50 pm)