- l4-hackers - example.com Site

I/O port protection
by Daniel Vandersee 12 Jan '07

12 Jan '07

Hi there, is it possible to allow I/O page mapping at the RMGR for a newly created task (using l4_task_new) as it were possible using the "allow_cli" flag in the roottask configuration? Usually the pager of the newly created task would handle its I/O pagefaults. Unfortunately this won't work here as this particular task (L4 loader) tries to directly map I/O pages using an IPC call to the ressource manager. So the question is: How can I tell the ressource manager to allow I/O mapping for this particular task? Thanks, Daniel

2 3

Documentation for L4Linux/L4Env
by Christian, Martin, OPEE45 11 Jan '07

11 Jan '07

Hi, is there some documentation on the L4Linux source code? A kind of what-does-what? I've seen L4Linux has been ported to ARM? Is there a porting guide? HowTo? Wiki? Something more than C or assembler? How much has L4Linux still in common with UML? Which parts were used and where are they now? Best, Martin.

2 1

Indirect IPC or direct IPC
by chenggh 10 Jan '07

10 Jan '07

Hi: Today I read the DICE Manual 3.1.0 and it talks about something about indirect IPC and direct IPC. According to my understanding it seems like this: indirect IPC: sender - > message buffer -> receiver direct IPC: sender ->sender buffer -> receive buffer ->receiver. But I think this understanding is wrong and I don't search something helpful by google, too. If somebody knows please tell me. In this manaul it says ln L4 version 4 all constructed data types will be transmitted by indirect IPC not direct IPC. I also want to know why. Thank you. Best wishes. cheng

3 2

Why I can't get the seconds and nanoseconds like this?
by chenggh 08 Jan '07

08 Jan '07

Hi: I wrote the simple application like this. #include <stdio.h> #include <l4/util/rdtsc.h> #include <l4/sys/l4int.h> #include <l4/thread/thread.h> char LOG_tag[4]="clk"; int main(void) { l4_uint32_t *second; l4_uint32_t *nanosecond; l4_cpu_time_t tsc; tsc = l4_rdtsc(); l4_tsc_to_s_and_ns(tsc, second, nanosecond); printf("%d, %d \n", *second, *nanosecond); } The result is : clk | 0, 0 clk | clk | Exiting with 6 Does these code have some problems? Thank you. cheng

3 2

Re: L4 Demo CD problems
by Dave Haddon 07 Jan '07

07 Jan '07

I am using a PC104 stack with a PIII/1Ghz, 256Mb, CD and 6Gig HD... no floppy..currently running timesys (6.1) (Linux Kernel 2.6.16.16 for i686) I eventually got the source for L4 to Compile by leaving out bits that were causing compiling errors.. RTC for example.. once I got to that point.. my hard drive died and I had to start from scratch.. arrgghh!!!! After much stuffing around to find a workable drive for the PC104, I figured I'd just download the Demo cd and have a whack at that, and it wouldn't work.. I'm starting to get a bit annoyed.. I originally retrieved the L4linux source from CVS, (l4 and linux-2.6) and tried to compile it together from the instructions on the DROPS web and had a lot of missing pieces in timesys, (mainly upto-date PERL and automake).. I haven't tried with QEMU or VMware as I have the PC104 on the same monitor and keyboard.. it is too easy to switch between the PC104 and my desktop (P4 2.8G, SuSe 9.3, KDE 3.4.0b..with no root permissions...) Any info you can give me would be greatly appreciated.. Dave Haddon On Fri, 2007-01-05 at 08:20 +0100, Bjoern Doebel wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > > I have downloaded and burnt the Demo CD exactly as described on the > > website, but it won't come up with the grub menu as described. All I get > > is the Grub command prompt. Have I done something wrong? I have been > > trying to get L4linux to work for ages now and nothing is working.. > > (Mainly a harddrive crash and a lack of root permissions on my main PC > > causing problems...) Can someone please help.. > > some more information about your system, what exactly you've been doing to > run L4Linux and what failures you encountered could be helpful. > And can you maybe try to run the DemoCD-Image in QEMU or VMWare? > > Bjoern > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFFnfxIP5ijxgQLUNkRAuKHAKCQBAHJbkFm6/GaBo7WCyMsnSY1LQCfcKbR > 3LKgzTHKSIU3HlfiEoHadIM= > =6eip > -----END PGP SIGNATURE----- -- CSIRO - Queensland Centre for Advanced Technologies Technology Court Pullenvale Qld 4069 AUSTRALIA PO Box 883 Kenmore Qld 4069 AUSTRALIA Telephone +61 7 3327 4444 Facsimile +61 7 3327 4455

2 1

L4 Demo CD problems
by Dave Haddon 05 Jan '07

05 Jan '07

I have downloaded and burnt the Demo CD exactly as described on the website, but it won't come up with the grub menu as described. All I get is the Grub command prompt. Have I done something wrong? I have been trying to get L4linux to work for ages now and nothing is working.. (Mainly a harddrive crash and a lack of root permissions on my main PC causing problems...) Can someone please help.. Thanks -- CSIRO - Queensland Centre for Advanced Technologies Technology Court Pullenvale Qld 4069 AUSTRALIA PO Box 883 Kenmore Qld 4069 AUSTRALIA Telephone +61 7 3327 4444 Facsimile +61 7 3327 4455

2 1

Problems compiling NICTA::Pistachio-embedded 1.3.0.
by Jaeheon Yi 01 Jan '07

01 Jan '07

Hello, I'm attempting to compile NICTA::Pistachio-embedded, version 1.3.0. I've downloaded the source using tla, via `tla get ertos(a)nicta.com.au--public/pistachio--release my_pistachio`. When I follow the standard L4 compile procedure and perform make, I get this message: [jaeheon@l4rbed ia32-kernel-build]$ make menuconfig dirname: too few arguments Try `dirname --help' for more information. bash: /gccgcc: No such file or directory make[1]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build' make[2]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build/config' Compiling rules, please wait......(0.72 sec) Done. Loading 'config.out' failed, continuing... Rewriting Makeconf.local ... make[2]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build/config' make[1]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build' [jaeheon@l4rbed ia32-kernel-build]$ make dirname: too few arguments Try `dirname --help' for more information. bash: /gccgcc: No such file or directory make[1]: Entering directory `/src/NICTA-1.3.0/ia32-kernel-build' make[1]: *** No rule to make target `src/generic/mapping_alloc.cc', needed by `.depend'. Stop. make[1]: Leaving directory `/src/NICTA-1.3.0/ia32-kernel-build' make: *** [all] Error 2 [jaeheon@l4rbed ia32-kernel-build]$ I've tried doing this for the ARM architecture ala Ben Leslie's L4 dev slides, and that also ends up not finding a certain file. I get the feeling that I am missing some files, or perhaps I have to tweak some config files? I would appreciate any pointers on this issue. Thank you, Jaeheon Yi

2 1

Re: What is difference among these 3 terms: domain, task and thread
by Adam Lackorzynski 29 Dec '06

29 Dec '06

Hi, On Wed Dec 27, 2006 at 16:16:57 +0800, chenggh wrote: > I want to know what is the difference among these 3 terms : domain, task and > thread in L4/Fiasco documents. If sb could understand please show me clearly. Where did you read 'domain' in a Fiasco document? A task is an address space which contains one or more threads. Pagetables are attached to tasks, threads execute code. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

What is difference among these 3 terms: domain, task and thread
by chenggh 27 Dec '06

27 Dec '06

Hi: I want to know what is the difference among these 3 terms : domain, task and thread in L4/Fiasco documents. If sb could understand please show me clearly. thank you. Best wishes. cheng

1 0

Re: failed to booting l4linux from serial console
by chenggh 23 Dec '06

23 Dec '06

> CPU: Intel Pentium III (Coppermine) stepping 03 > 0000 [#1] > Modules linked in: > CPU: 0 > EIP: fd10:[<00501eb0>] Not tainted VLI > EFLAGS: 00213202 (2.6.18-l4 #22) > EIP is at _mmx_memcpy+0x30/0x150 > eax: bff00200 ebx: 00000014 ecx: 00000064 edx: 010cfa84 > esi: 0064d924 edi: 00000200 ebp: 010cdd94 esp: 010cdd84 > ds: fd24 es: 0890 ss: 0000 > Process swapper (pid: 1, ti=010cc000 task=010caa70 task.ti=010cc000) > Stack: 00000014 010ca550 fffffff4 00000200 010cde04 004132e4 010cfa84 > 0064d924 00000500 00000000 00000000 ffffffff ffffffff 010cc038 010ca610 > 010cde5c 00000000 10800711 00000000 010ca550 000000d0 00000000 010c93a8 > 010c93a8 Call Trace: > [<0040c449>] show_stack_log_lvl+0xa9/0xd0 > [<0040c61a>] show_registers+0x15a/0x1c0 > [<0040c795>] die+0x115/0x2d0 > [<00000000>] _start+0xffc00000/0x50 > [<004132e4>] copy_process+0x954/0xfb0 > [<00413b2b>] do_fork+0x6b/0x1c0 > [<004092ba>] kernel_thread+0x7a/0x90 > [<00427707>] keventd_create_kthread+0x27/0x70 > [<0042791a>] kthread_create+0xda/0xe0 > [<0069e226>] cpu_callback+0x76/0xd0 > [<0069e2a2>] spawn_ksoftirqd+0x22/0x50 > [<004001cc>] init+0x1c/0x280 > [<00408960>] kernel_thread_start+0x30/0x40 > [<004084e6>] ret_kernel_thread_start+0x6/0x10 > Code: 53 83 ec 04 8b 75 0c 89 e0 25 00 e0 ff ff f7 40 14 00 ff ff 0f 0f 85 > 11 01 00 00 8b 45 10 c1 e8 06 89 45 f0 89 c3 e8 30 43 f0 ff <0f> 0d 06 0f > 0d 46 40 0f 0d 86 80 00 00 00 0f 0d 86 c0 00 00 00 > EIP: [<00501eb0>] _mmx_memcpy+0x30/0x150 SS:ESP 0023:010cdd7c > <0>Kernel panic - not syncing: Attempted to kill init! > panic: going to sleep forever, bye Right now I forget to tell you my CPU type is Duron. Do you change the cpu type in my configuration? And I suggest in the first time you should use the com1 to display the l4 output information and after you check that the l4 booting is correct you use the com1 to display the l4linux output inforamtion instead of l4. It seems that you have only one serial console. :) it is bad. cheng cheng

1 0