* [Xenomai] ipipe_read_tsc, ipipe_tsc2ns
@ 2015-09-29 12:38 Johann Obermayr
2015-09-29 13:33 ` Gilles Chanteperdrix
2015-09-29 13:36 ` Henning Schild
0 siblings, 2 replies; 4+ messages in thread
From: Johann Obermayr @ 2015-09-29 12:38 UTC (permalink / raw)
To: xenomai
Hello,
in a loadable kernel module i use ipipe_read_tsc and ipipe_tsc2ns.
But at compiling i get follow warning.
WARNING: "__ipipe_kuser_tsc_freq" [km_testsample.ko] undefined!
we have ARM, Linux 3.0 + xenomai 2.6.2.1
Best reagards,
Johann
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] ipipe_read_tsc, ipipe_tsc2ns
2015-09-29 12:38 [Xenomai] ipipe_read_tsc, ipipe_tsc2ns Johann Obermayr
@ 2015-09-29 13:33 ` Gilles Chanteperdrix
2015-09-29 13:36 ` Henning Schild
1 sibling, 0 replies; 4+ messages in thread
From: Gilles Chanteperdrix @ 2015-09-29 13:33 UTC (permalink / raw)
To: Johann Obermayr; +Cc: xenomai
On Tue, Sep 29, 2015 at 02:38:58PM +0200, Johann Obermayr wrote:
> Hello,
>
> in a loadable kernel module i use ipipe_read_tsc and ipipe_tsc2ns.
> But at compiling i get follow warning.
>
> WARNING: "__ipipe_kuser_tsc_freq" [km_testsample.ko] undefined!
>
> we have ARM, Linux 3.0 + xenomai 2.6.2.1
These are I-pipe internal functions. You should be using Xenomai
API:
- If developing a driver, you should be using rtdm_clock_read(),
- if using the deprecated kernel-space native API, rt_timer_tsc()
/ rt_timer_tsc2ns
- if using the deprecated kernel-space posix API,
clock_gettime(CLOCK_MONOTONIC).
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] ipipe_read_tsc, ipipe_tsc2ns
2015-09-29 12:38 [Xenomai] ipipe_read_tsc, ipipe_tsc2ns Johann Obermayr
2015-09-29 13:33 ` Gilles Chanteperdrix
@ 2015-09-29 13:36 ` Henning Schild
2015-09-29 13:40 ` Gilles Chanteperdrix
1 sibling, 1 reply; 4+ messages in thread
From: Henning Schild @ 2015-09-29 13:36 UTC (permalink / raw)
To: Johann Obermayr; +Cc: xenomai
On Tue, 29 Sep 2015 14:38:58 +0200
Johann Obermayr <johann.obermayr@sigmatek.at> wrote:
> in a loadable kernel module i use ipipe_read_tsc and ipipe_tsc2ns.
> But at compiling i get follow warning.
>
> WARNING: "__ipipe_kuser_tsc_freq" [km_testsample.ko] undefined!
>
> we have ARM, Linux 3.0 + xenomai 2.6.2.1
You should be able to resolve that linking problem by exporting the
missing symbol.
Add a "EXPORT_SYMBOL_GPL(__ipipe_kuser_tsc_freq);" after its definition.
Henning
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] ipipe_read_tsc, ipipe_tsc2ns
2015-09-29 13:36 ` Henning Schild
@ 2015-09-29 13:40 ` Gilles Chanteperdrix
0 siblings, 0 replies; 4+ messages in thread
From: Gilles Chanteperdrix @ 2015-09-29 13:40 UTC (permalink / raw)
To: Henning Schild; +Cc: xenomai
On Tue, Sep 29, 2015 at 03:36:40PM +0200, Henning Schild wrote:
> On Tue, 29 Sep 2015 14:38:58 +0200
> Johann Obermayr <johann.obermayr@sigmatek.at> wrote:
>
> > in a loadable kernel module i use ipipe_read_tsc and ipipe_tsc2ns.
> > But at compiling i get follow warning.
> >
> > WARNING: "__ipipe_kuser_tsc_freq" [km_testsample.ko] undefined!
> >
> > we have ARM, Linux 3.0 + xenomai 2.6.2.1
>
> You should be able to resolve that linking problem by exporting the
> missing symbol.
> Add a "EXPORT_SYMBOL_GPL(__ipipe_kuser_tsc_freq);" after its definition.
The functions ipipe_tsc2us/tsc2ns are really internal functions for
the I-pipe tracer, I am not sure we want to expose this interface.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-09-29 13:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-29 12:38 [Xenomai] ipipe_read_tsc, ipipe_tsc2ns Johann Obermayr
2015-09-29 13:33 ` Gilles Chanteperdrix
2015-09-29 13:36 ` Henning Schild
2015-09-29 13:40 ` Gilles Chanteperdrix
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.