From: Vara Prasad <prasadav@us.ibm.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
SystemTAP <systemtap@sources.redhat.com>
Subject: Re: [2.6.19 patch] i386/x86_64: remove the unused EXPORT_SYMBOL(dump_trace)
Date: Fri, 24 Nov 2006 21:51:00 -0000 [thread overview]
Message-ID: <4563FED4.10000@us.ibm.com> (raw)
Message-ID: <20061124215100.ia_yXbzoYpFRQFr-LaONiVgw1POYGUU2OD6RNwuMZZ4@z> (raw)
In-Reply-To: <20061121210622.6cea428f@localhost.localdomain>
Alan wrote:
>On Tue, 21 Nov 2006 20:18:44 +0000
>Christoph Hellwig <hch@infradead.org> wrote:
>
>
>
>>On Tue, Nov 21, 2006 at 08:47:30PM +0100, Andi Kleen wrote:
>>
>>
>>>On Tuesday 21 November 2006 20:41, Adrian Bunk wrote:
>>>
>>>
>>>>This patch removes the unused EXPORT_SYMBOL(dump_trace) added on i386
>>>>and x86_64 in 2.6.19-rc.
>>>>
>>>>By removing them before the final 2.6.19 we avoid the possibility of
>>>>people later whining that we removed exports they started using.
>>>>
>>>>
>>>I exported it for systemtap so that they can stop using the broken
>>>hack they currently use as unwinder.
>>>
>>>
>>Nack, dump_trace is nothing that should be export for broken out of tree
>>junk.
>>
>>
>
>It is exported for systemtap not random broken out of tree junk, and the
>result is a good deal prettier. Systemtap guys really ought to get their
>stuff merged too, although how we merge a dynamic module writing tool I'm
>not so sure ?
>
>
>
As you all know SystemTap uses kprobes and relayfs as the basis which
are already merged into the mainline.
We are looking at all the other pieces of SystemTap that can be merged
to mainline but as Alan mentioned it is not easy and obvious. We think
we can merge transport part of the runtime, here is the initial patch
under review in this thread
http://sources.redhat.com/ml/systemtap/2006-q4/msg00031.html
http://sources.redhat.com/ml/systemtap/2006-q4/msg00030.html
We are open for other suggestions as well.
bye,
Vara Prasad
>Alan
>-
>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/
>
>
>
-
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/
next parent reply other threads:[~2006-11-22 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061121194138.GF5200@stusta.de>
[not found] ` <200611212047.30192.ak@suse.de>
[not found] ` <20061121201844.GA7099@infradead.org>
[not found] ` <20061121210622.6cea428f@localhost.localdomain>
2006-11-22 21:33 ` Vara Prasad [this message]
2006-11-24 21:51 ` Vara Prasad
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=4563FED4.10000@us.ibm.com \
--to=prasadav@us.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sources.redhat.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).