Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: Exports for hrtimer APIs
Date: Tue, 14 Mar 2006 13:15:52 -0800
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06A92A64@scsmsx403.amr.corp.intel.com>
Thread-Topic: Exports for hrtimer APIs
Thread-Index: AcZHfFylKEpn3Q3fQ1qc5dNOrYasUAALqpqg
From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 932
Lines: 25

Christoph Hellwig wrote:
> NACK.  We only add exports when they are a) sensible and b) are used
> in kernel.

It seems to me that SystemTap does present a sensible need to have
these exports.

> If you guys want to keep your code out of tree that's your problem.

I'm not sure what else you would suggest for this usage model.
SystemTap dynamically generates modules based on user scripts, so
this isn't something that can be added to the tree.

If SystemTap is to be able to make use of hrtimers, the only alternative
I see is to create our own APIs in the tree that wrap hrtimer, and then
export those.  This seems much less sensible than just exporting what is
already there...


Josh
-
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/