[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070921133006.GF8964@redhat.com>
Date: Fri, 21 Sep 2007 09:30:07 -0400
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Denys Vlasenko <vda.linux@...glemail.com>, dsmith@...hat.com,
Christoph Hellwig <hch@...radead.org>,
Rusty Russell <rusty@...tcorp.com.au>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 1/4] Linux Kernel Markers - Architecture Independent Code
Hi -
On Fri, Sep 21, 2007 at 08:58:19AM -0400, Mathieu Desnoyers wrote:
> [...]
> > > Current systemtap marker support code relies on the __markers_strings
> > > section.
> > Let users know that in comment above section definition in ld script.
> [...]
> /* Markers: strings (used by SystemTAP) */ \
> [...]
I did not mean to imply that this was a necessary state of affairs.
The marker metadata must be stored in at least one place in the kernel
image - this just happens to be a convenient one that David Smith's
recent systemtap code used. Without it, we'd probably have to do a
more complicated search, following the pointers within the __markers
structs. That could work, but it hasn't been built/tested.
So, this proposed change (removal of this section) would break
systemtap, and we have to jump through more hoops to make it work
again. Is the change worth it?
- FChE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists