Re: [Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

2016-12-15 Thread Ronny Meeus
On Thu, Dec 15, 2016 at 6:25 PM, Philippe Gerum wrote: > On 12/15/2016 05:16 PM, Ronny Meeus wrote: >> On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum wrote: >>> On 12/15/2016 12:47 PM, Ronny Meeus wrote: bootstrap.o is linked to the application code. In case the execution of the static

Re: [Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

2016-12-15 Thread Philippe Gerum
On 12/15/2016 05:16 PM, Ronny Meeus wrote: > On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum wrote: >> On 12/15/2016 12:47 PM, Ronny Meeus wrote: >>> bootstrap.o is linked to the application code. >>> In case the execution of the static constructors is postponed >>> in the applicaion and the auto-

Re: [Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

2016-12-15 Thread Ronny Meeus
On Thu, Dec 15, 2016 at 3:47 PM, Philippe Gerum wrote: > On 12/15/2016 12:47 PM, Ronny Meeus wrote: >> bootstrap.o is linked to the application code. >> In case the execution of the static constructors is postponed >> in the applicaion and the auto-init feature is used, the >> xenomai_init is call

Re: [Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

2016-12-15 Thread Philippe Gerum
On 12/15/2016 12:47 PM, Ronny Meeus wrote: > bootstrap.o is linked to the application code. > In case the execution of the static constructors is postponed > in the applicaion and the auto-init feature is used, the > xenomai_init is called 2 times: > - once in the path of the wrap_main > - later in

Re: [Xenomai] __map_umm return NULL

2016-12-15 Thread Philippe Gerum
On 12/15/2016 10:59 AM, Julien Stephan wrote: > Hello, > > As explained in my previous question "TIP_HEAD bit during Xenomai > initialization" I am porting xenomai 3 on a new architecture. > > > My problem here is that the function __map_umm return NULL. This cause a > SEGV in cobalt_commit_memo

Re: [Xenomai] Mercury: roundrobin scheduling using Linux scheduler.

2016-12-15 Thread Philippe Gerum
On 12/15/2016 01:47 PM, Ronny Meeus wrote: > On Fri, Dec 9, 2016 at 11:48 AM, Philippe Gerum wrote: >> On 12/06/2016 03:56 PM, Ronny Meeus wrote: >>> Hello >>> >>> Round-robin scheduling is implemented in Mercury by >>> starting a per-thread timer that sends a signal to the thread >>> when its bud

Re: [Xenomai] Mercury: roundrobin scheduling using Linux scheduler.

2016-12-15 Thread Ronny Meeus
On Fri, Dec 9, 2016 at 11:48 AM, Philippe Gerum wrote: > On 12/06/2016 03:56 PM, Ronny Meeus wrote: >> Hello >> >> Round-robin scheduling is implemented in Mercury by >> starting a per-thread timer that sends a signal to the thread >> when its budget is consumed. >> >> There are several good reaso

[Xenomai] [PATCH] boilerplate: do not call xenomai_init 2 times

2016-12-15 Thread Ronny Meeus
bootstrap.o is linked to the application code. In case the execution of the static constructors is postponed in the applicaion and the auto-init feature is used, the xenomai_init is called 2 times: - once in the path of the wrap_main - later in the context of the static constructor A check is alre

[Xenomai] [PATCH v2] boilerplate: Limit memory usage tlsf-heap

2016-12-15 Thread Ronny Meeus
Before this patch the system memory pool's (tlsf variant) behavior was to grow in case allocations were done when depleted. This is a contradiction with the expected behavior (see mem-pool-size tunable documentation). When the pool is depleted, an error should be retuned instead of growing the pool

[Xenomai] __map_umm return NULL

2016-12-15 Thread Julien Stephan
Hello, As explained in my previous question "TIP_HEAD bit during Xenomai initialization" I am porting xenomai 3 on a new architecture. My problem here is that the function __map_umm return NULL. This cause a SEGV in cobalt_commit_memory. I step into __map_umm with gdb and noticed that there is