Dear all,
Greetings of New Year 2006!
I presume that this is the right mailing list to ask
about the fundamental characteristics of Xenomai, a
very promising RTOS. If I'm wrong please forward it to
right place since I'm going to invite a group of
people to implement Xenomai -;)
1. Xenomai and R
Hi,
the current RTDM profile headers (so far only rtserial.h and
rtbenchmark.h) suffer from the "xenomai" prefix in the include path.
This was introduced with 2.1. An example: rtserial.h contains "#include
" which is fine in kernel space but requires that -
in my eyes - ugly "xenomai"->"." link in
Jan Kiszka wrote:
Hi,
the current RTDM profile headers (so far only rtserial.h and
rtbenchmark.h) suffer from the "xenomai" prefix in the include path.
This was introduced with 2.1. An example: rtserial.h contains "#include
" which is fine in kernel space but requires that -
in my eyes - ugly "x
Hi,
I'm trying to use the xeno_timerbench as a replacement to the old 2.0
klatency module and I encounter some problems.
This is on my in-progress ARM Xenomai port. User space latency and old
klatency work great (my board has some hardware latency problems though
- latencies can be as high as 500
Hi,
As I've noticed, the tracer ist still not compeletly in the SVN trunk.
Thus it causes some problems (missing header files) while compiling the
timer Benchmark module.
Here is a small patch, which fix this problem.
Cheers
Luotao Fu
diff -uNr xenomai/ksrc/drivers/benchmark/timerbench.c xenomai-w
Luotao Fu wrote:
Hi,
As I've noticed, the tracer ist still not compeletly in the SVN trunk.
And it won't actually. It is an optional part of the I-pipe layer.
Thus it causes some problems (missing header files) while compiling the
timer Benchmark module.
Here is a small patch, which fix thi
Stelian Pop wrote:
> Hi,
>
> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> klatency module and I encounter some problems.
>
> This is on my in-progress ARM Xenomai port. User space latency and old
> klatency work great (my board has some hardware latency problems though
Le mercredi 04 janvier 2006 à 17:49 +0100, Jan Kiszka a écrit :
> Stelian Pop wrote:
> > Hi,
> >
> 88> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> > klatency module and I encounter some problems.
> >
> > This is on my in-progress ARM Xenomai port. User space latency an
Stelian Pop wrote:
> Before hanging, sometimes it just prints:
> Unable to handle kernel NULL pointer dereference at virtual address
> 004d
>
> Sometimes the oops is more complete (note that sometimes it also hangs in
> the middle of
> the printout):
> Unable to handle kern
Le mercredi 04 janvier 2006 à 18:19 +0100, Gilles Chanteperdrix a
écrit :
> Stelian Pop wrote:
> > Before hanging, sometimes it just prints:
> >Unable to handle kernel NULL pointer dereference at virtual address
> 004d
> >
> > Sometimes the oops is more complete (note that sometimes i
Hi all,
after a long day of experimenting with a new tracer revision (will get
posted later), I'm looking now for some external wisdom.
I changed the instrumentation for high-domain stall times such that I
now attach to local_irq_disable_hw & friends instead. In case the
hard-IRQ status doesn't c
Hi again,
here comes the first update of the new latency tracer.
arch/i386/kernel/entry.S | 27 +++
arch/i386/kernel/ipipe-root.c |4
include/asm-i386/system.h | 70 +
include/linux/ipipe_trace.h |3
kernel/ipipe/Kconfig | 18 ++
kernel/ipipe/tracer.c
Jan Kiszka wrote:
> Hi all,
>
> after a long day of experimenting with a new tracer revision (will get
> posted later), I'm looking now for some external wisdom.
>
> I changed the instrumentation for high-domain stall times such that I
> now attach to local_irq_disable_hw & friends instead. In ca
hi Phillipe, everyone,
happy 06 !
Out of curiosity, I applied adeos-ipipe-2.6.14-i386-1.1-01.patch on top
of 15.
the rejects were small, and simple enough looking, that even
a lazy sod like myself might manually fix them, so I did.
whats more, it built clean and booted !
I havent done anythi
Dear all,
Greetings of New Year 2006!
I presume that this is the right mailing list to ask
about the fundamental characteristics of Xenomai, a
very promising RTOS. If I'm wrong please forward it to
right place since I'm going to invite a group of
people to implement Xenomai -;)
1. Xenomai and R
Hi,
the current RTDM profile headers (so far only rtserial.h and
rtbenchmark.h) suffer from the "xenomai" prefix in the include path.
This was introduced with 2.1. An example: rtserial.h contains "#include
" which is fine in kernel space but requires that -
in my eyes - ugly "xenomai"->"." link in
Jan Kiszka wrote:
Hi,
the current RTDM profile headers (so far only rtserial.h and
rtbenchmark.h) suffer from the "xenomai" prefix in the include path.
This was introduced with 2.1. An example: rtserial.h contains "#include
" which is fine in kernel space but requires that -
in my eyes - ugly "x
Hi,
I'm trying to use the xeno_timerbench as a replacement to the old 2.0
klatency module and I encounter some problems.
This is on my in-progress ARM Xenomai port. User space latency and old
klatency work great (my board has some hardware latency problems though
- latencies can be as high as 500
Hi,
As I've noticed, the tracer ist still not compeletly in the SVN trunk.
Thus it causes some problems (missing header files) while compiling the
timer Benchmark module.
Here is a small patch, which fix this problem.
Cheers
Luotao Fu
diff -uNr xenomai/ksrc/drivers/benchmark/timerbench.c xenomai-w
Stelian Pop wrote:
> Hi,
>
> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> klatency module and I encounter some problems.
>
> This is on my in-progress ARM Xenomai port. User space latency and old
> klatency work great (my board has some hardware latency problems though
Luotao Fu wrote:
Hi,
As I've noticed, the tracer ist still not compeletly in the SVN trunk.
And it won't actually. It is an optional part of the I-pipe layer.
Thus it causes some problems (missing header files) while compiling the
timer Benchmark module.
Here is a small patch, which fix thi
Le mercredi 04 janvier 2006 à 17:49 +0100, Jan Kiszka a écrit :
> Stelian Pop wrote:
> > Hi,
> >
> 88> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> > klatency module and I encounter some problems.
> >
> > This is on my in-progress ARM Xenomai port. User space latency an
Stelian Pop wrote:
> Before hanging, sometimes it just prints:
> Unable to handle kernel NULL pointer dereference at virtual address
> 004d
>
> Sometimes the oops is more complete (note that sometimes it also hangs in
> the middle of
> the printout):
> Unable to handle kern
Le mercredi 04 janvier 2006 à 18:19 +0100, Gilles Chanteperdrix a
écrit :
> Stelian Pop wrote:
> > Before hanging, sometimes it just prints:
> >Unable to handle kernel NULL pointer dereference at virtual address
> 004d
> >
> > Sometimes the oops is more complete (note that sometimes i
Hi all,
after a long day of experimenting with a new tracer revision (will get
posted later), I'm looking now for some external wisdom.
I changed the instrumentation for high-domain stall times such that I
now attach to local_irq_disable_hw & friends instead. In case the
hard-IRQ status doesn't c
Hi again,
here comes the first update of the new latency tracer.
arch/i386/kernel/entry.S | 27 +++
arch/i386/kernel/ipipe-root.c |4
include/asm-i386/system.h | 70 +
include/linux/ipipe_trace.h |3
kernel/ipipe/Kconfig | 18 ++
kernel/ipipe/tracer.c
Jan Kiszka wrote:
> Hi all,
>
> after a long day of experimenting with a new tracer revision (will get
> posted later), I'm looking now for some external wisdom.
>
> I changed the instrumentation for high-domain stall times such that I
> now attach to local_irq_disable_hw & friends instead. In ca
27 matches
Mail list logo
