Re: Physical memory allocation to L4linux

2014-09-16 Thread Masti Ramya Jayaram
Hey Adam, Yes I can confirm that I was a able to trace the code from fpage_map() to map() but I see zero addresses there - i.e. When I check the receiver and sender addresses and size everything is zero. This was despite it being correct until the handle_sigma0_request() function in

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Valentin Hauner
Hi, On 09/16/2014 12:04 AM, Adam Lackorzynski wrote: Are there any entries? Yes, there are produced more than thousand identical entries in less than a second: pf: 0026 pfa=4f3c ip=01000200 (w-) spc=0xfcffae94 err=6 '26' is the id of the thread that is waiting for '1b'. On

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.09.2014 13:15, Valentin Hauner wrote: Hi, On 09/16/2014 12:04 AM, Adam Lackorzynski wrote: Are there any entries? Yes, there are produced more than thousand identical entries in less than a second: pf: 0026 pfa=4f3c ip=01000200

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Valentin Hauner
Hi, thanks again for your quick reply! On 09/16/2014 01:21 PM, Björn Döbel wrote: * What is this instruction? * What address is this? It does not seem to be part of the binary as it is far off the instruction address. * Does this page fault appear in your pager? (It should?) * What are

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.09.2014 13:40, Valentin Hauner wrote: Hi, thanks again for your quick reply! On 09/16/2014 01:21 PM, Björn Döbel wrote: * What is this instruction? * What address is this? It does not seem to be part of the binary as it is far off the

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Valentin Hauner
Hi, thanks, I've used addr2line and found out that it was the head of thread_func (l. 27 in examples/libedft-example/main.c). So it seems that the stack I'm using for passing arguments to the thread function is the problem. As I am creating a dynamic number of threads, it does not make sense for

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.09.2014 15:26, Valentin Hauner wrote: Hi, thanks, I've used addr2line and found out that it was the head of thread_func (l. 27 in examples/libedft-example/main.c). So it seems that the stack I'm using for passing arguments to the thread

Re: l4/sys/syscalls.h: No such file or directory

2014-09-16 Thread Valentin Hauner
Hi, On 09/16/2014 03:54 PM, Björn Döbel wrote: Just to be sure: How large is this per-thread stack? Are you properly aligning it to page boundaries? Adam suggested to give it a size of 2000 * l4_umword_t (THREAD_STACK_SIZE is set to 2000) in his mail from September 3th, so I'm using the

Trimming uclibc in l4

2014-09-16 Thread Masti Ramya Jayaram
Dear all, I would like to extract the minimal subset of uclibc required by bootstrap, sigma and their dependencies only. My idea is to have these modules use the smaller libc while retain the usual uclibc build for the other packages. I intend to go about this by copying uclibc (say into

RE: Trimming uclibc in l4

2014-09-16 Thread Masti Ramya Jayaram
Update: turns out it is not very simple to compile just bootstrap against a smaller library because the l4/mk/modes.inc file defaults to the uclibc library for compiling the files which is used for all packages. Any ideas how I can change this only for some packages? Thanks. Ramya

RE: Trimming uclibc in l4

2014-09-16 Thread Masti Ramya Jayaram
Hey Markus, I am using a version from April 2011 but even that version contains a lot of things that bootstrap and sigma0 do not need. :) Did you mean more recent than that? best, ramya p.s. my board requires that I run an older version of the kernel - so the pain.

Re: Trimming uclibc in l4

2014-09-16 Thread Björn Döbel
Hi, as Marcus already pointed out, newer versions of L4Re actually contain a package called uclibc_minimal that serves exactly this purpose. Even if you are using an older snapshot, chances are that backporting this package (and adapting l4/mk) might be easier than stripping things down

RE: Trimming uclibc in l4

2014-09-16 Thread Marcus Hähnel
Hi Ramya, On 2014-09-16 19:05, Masti Ramya Jayaram wrote: Hey Markus, I am using a version from April 2011 but even that version contains a lot of things that bootstrap and sigma0 do not need. :) Did you mean more recent than that? this version is severely outdated :x. Please use a recent