Richard Cochran wrote:
On Mon, Apr 11, 2011 at 11:26:33PM +0200, Gilles Chanteperdrix wrote:
Wait a minute. You are comparing results obtained after 2 or 3, or 10
minutes of runtime? I am not sure such results are meaningful. I do my
benchmarks with the noltp_hell test:
On Tue, Apr 12, 2011 at 09:17:43AM +0200, Gilles Chanteperdrix wrote:
What compiler are you using by the way?
I compiled this one myself using crosstool-ng. At the time I had first
tried gcc 4.3, but you advised me that it would not work for xenomai.
Target: armeb-unknown-linux-gnueabi
Richard Cochran wrote:
On Tue, Apr 12, 2011 at 09:17:43AM +0200, Gilles Chanteperdrix wrote:
What compiler are you using by the way?
I compiled this one myself using crosstool-ng. At the time I had first
tried gcc 4.3, but you advised me that it would not work for xenomai.
All codesourcery
I have managed to print the stack of a faulting thread:
Xenomai: suspending kernel thread b911f518 ('rtnet-rtpc') at
nip=0xb911f940, lr=0xb911f940, r1=0xaf2c4580 after exception #1792
Xenomai: dumping stack at af2c4600
Xenomai: 0xaf2c45ec - 0xaf2c45fc: af2c4600 8009a334
Jesper Christensen wrote:
I have managed to print the stack of a faulting thread:
Did you test the patch I directed you to? We may be chasing an already
known issue here...
--
Gilles.
___
Xenomai-core
On 2011-04-12 15:31, Jesper Christensen wrote:
I have managed to print the stack of a faulting thread:
Xenomai: suspending kernel thread b911f518 ('rtnet-rtpc') at
nip=0xb911f940, lr=0xb911f940, r1=0xaf2c4580 after exception #1792
Xenomai: dumping stack at af2c4600
Xenomai:
Sorry about that, yes i merged that in right away.
/Jesper
On 2011-04-12 15:39, Gilles Chanteperdrix wrote:
Jesper Christensen wrote:
I have managed to print the stack of a faulting thread:
Did you test the patch I directed you to? We may be chasing an already
known issue
Unfortunately it's not part of the tar ball, but i might be able to post
a source file that sums it up pretty well.
/Jesper
On 2011-04-12 15:40, Jan Kiszka wrote:
On 2011-04-12 15:31, Jesper Christensen wrote:
I have managed to print the stack of a faulting thread:
Xenomai:
Speaking of rtpc, could there be a race condition when using a
rtdm_lock_t to synchronize between a linux thread and a xenomai thread?
/Jesper
On 2011-04-12 15:40, Jan Kiszka wrote:
On 2011-04-12 15:31, Jesper Christensen wrote:
I have managed to print the stack of a faulting thread:
On 2011-04-12 16:09, Jesper Christensen wrote:
Speaking of rtpc, could there be a race condition when using a
rtdm_lock_t to synchronize between a linux thread and a xenomai thread?
Without seeing at some code, I can't comment on this meaningfully.
Jan
--
Siemens AG, Corporate Technology, CT
There you go:
---
#include linux/module.h
#include linux/kernel.h
#include linux/list.h
#include linux/workqueue.h
#include rtnet_rtpc.h
#include up.h
static rtdm_lock_t umsg_list_lock = RTDM_LOCK_UNLOCKED;
On 2011-04-12 16:21, Jesper Christensen wrote:
There you go:
---
#include linux/module.h
#include linux/kernel.h
#include linux/list.h
#include linux/workqueue.h
#include rtnet_rtpc.h
#include up.h
On 2011-04-12 17:24, Jan Kiszka wrote:
On 2011-04-12 16:21, Jesper Christensen wrote:
There you go:
---
#include linux/module.h
#include linux/kernel.h
#include linux/list.h
#include linux/workqueue.h
13 matches
Mail list logo
