From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
dsmith@redhat.com, Christoph Hellwig <hch@infradead.org>,
Rusty Russell <rusty@rustcorp.com.au>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/4] Linux Kernel Markers - Architecture Independent Code
Date: Fri, 21 Sep 2007 09:30:07 -0400 [thread overview]
Message-ID: <20070921133006.GF8964@redhat.com> (raw)
In-Reply-To: <20070921125819.GA13129@Krystal>
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
next prev parent reply other threads:[~2007-09-21 13:31 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 21:13 [patch 0/4] Linux Kernel Markers for 2.6.23-rc6-mm1 Mathieu Desnoyers
2007-09-18 21:13 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-09-19 11:37 ` Mathieu Desnoyers
2007-09-19 13:53 ` Frank Ch. Eigler
2007-09-19 20:32 ` Denys Vlasenko
2007-09-21 12:58 ` Mathieu Desnoyers
2007-09-21 13:07 ` Christoph Hellwig
2007-09-21 13:30 ` Frank Ch. Eigler [this message]
2007-09-21 13:38 ` Mathieu Desnoyers
2007-10-15 19:41 ` Frank Ch. Eigler
2007-10-15 23:12 ` Mathieu Desnoyers
2007-10-15 23:50 ` Roland McGrath
2007-10-25 19:17 ` Mathieu Desnoyers
2007-10-26 14:28 ` Frank Ch. Eigler
2007-11-01 1:06 ` [PATCH] markers: modpost Roland McGrath
2007-11-01 2:46 ` Mathieu Desnoyers
2007-11-01 9:37 ` Roland McGrath
2007-11-01 11:24 ` Mathieu Desnoyers
2007-11-08 19:31 ` David Smith
2007-11-08 19:36 ` Mathieu Desnoyers
2007-11-08 19:45 ` David Smith
2007-11-09 16:36 ` David Smith
2007-11-11 23:24 ` Mathieu Desnoyers
2007-09-19 17:32 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Denys Vlasenko
2007-09-19 18:46 ` Mathieu Desnoyers
2007-09-19 18:50 ` Mathieu Desnoyers
2007-09-21 0:58 ` Steven Rostedt
2007-09-21 13:45 ` Mathieu Desnoyers
2007-09-18 21:13 ` [patch 2/4] Linux Kernel Markers - Use instrumentation kconfig menu Mathieu Desnoyers
2007-09-18 21:13 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-09-18 23:22 ` Randy Dunlap
2007-09-19 11:18 ` Mathieu Desnoyers
2007-09-18 21:13 ` [patch 4/4] Port of blktrace to the Linux Kernel Markers Mathieu Desnoyers
2007-09-21 1:03 ` Steven Rostedt
2007-09-21 13:46 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 18:46 [patch 0/4] " Mathieu Desnoyers
2007-09-17 18:46 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-08-27 16:05 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-27 16:05 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-08-20 20:27 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-20 20:27 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-08-21 0:43 ` Rusty Russell
2007-08-24 16:26 ` Mathieu Desnoyers
2007-08-25 20:49 ` Rusty Russell
2007-08-25 21:26 ` Mathieu Desnoyers
2007-08-12 15:10 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-12 15:10 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
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=20070921133006.GF8964@redhat.com \
--to=fche@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dsmith@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=rusty@rustcorp.com.au \
--cc=vda.linux@googlemail.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 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.