- l4-hackers - example.com Site

Re: Problem booting l4linux
by chenggh 28 Feb '07

28 Feb '07

On Wednesday 28 February 2007 11:12, Eduard Benes wrote: > Hi all, > > I'm newbie in this area, and I would like to ask for help with some > problems I run into (hope this is the right place). I've finally build > l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". > (please let me know if there is better document to start with) > dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. We have tested this document many times and some Linux newbie used this document to build the L4Linux very successfully. And please pay attention that this document is made in the case of kernel 2.6.17. Maybe in the kernel 2.6.19 there are some problems, too. > I had some problem finding out the right configuration of the > l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). > Right now I'm trying to run it on real hw (How to make it run under qemu?) > but when I try to boot DOpE using patched grub, it hangs when (at least I > assume) trying to enter graphic mode. The screen shows this: If you use L4Linux or Fiasco the first thing is to study how to use serial console to debug the Fiasco especially in the graphical mode you don't see anything important in the screen. Some booting error messages could only be output by the serial console. > I've tried the L4Linux demo CD, but with the same result. Tried to boot > into DOpE or console. I suspect that video card might not be supported. But > during many attempts, once the DOpE environment flashed for a second > (before doing the restart routine accidentally) and that really surprise > for me. The graphical user interface is not necessary, but I don't know yet > how to run L4Linux in console. I'm able to get into kernel debugger, when I > boot the L4Linux by remote serial console variant of grub menu.lst entries > (based on the kickstart document mentioned above). In the kernel debugger > mode was logged one error: > [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): > Error: Missing 'deceit_bit_disables_switch' kernel feature! > Startup: semaphore lib initialization failed (-1)! > It is probably not related to the problem with video card, but might show > some mistakes in my l4linux-2.6 kernel configuration. > If you still have some problems about compiling or booting, please download this tar ball (http://dslab.lzu.edu.cn/~chenggh/doc/L4.tar) I have tested this tar ball many times successfully and if you use this directory and do as the kickstart says. I promise you could be successful. In this letter there are 2 attachments: one is 2.4.17 configuration file for booting from serial console and another is 2.4.17 configuration file for booting from Dope. > My final goal is to compare performance of L4Linux and native Linux on real > hw. I will appreciate any suggestions or study literature on this topic. I have done some similar work as you want to do and if you want know something about my paper and data please access my home page (dslab.lzu.edu.cn/~chenggh). > Other questions I would like to ask: > What is the right way to boot from serial console? Please review my kickstart and some configuration file. > How can be achieved networking under L4Linux? In my benchmark about performance comparasion between L4Linux and Linux I use L4Linux network (It is same as you do in Linux). But if you want to use Fiasco network there is a module ORe (the Oshkosh Resurrection) you could try. But I think this module only show us the Fiasco supports network, too and you don't do anything meaningful. Thank you. I hope you could modify my kickstart and give the new version of this kickstart. Thank you. cheng

1 0

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

3 2

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Greetings, I have had some interest in os development and theory for quite some time now, and a particular interest in L4. I'm a newbie, but I've read through a lot, and have done some os programming for fun in the past. My question is: what is your advice on learning and hacking L4? I've read through quite a bit of the documentation, but reading through specs does not seem like a good way to really understand; it seems like too much to digest at once. And of course, the purpose of a specification is to specify, not explain. I've browsed through source code, but that is even worse. I'm sorry if my question is overly broad, but I'd appreciate any advice that anyone can spare. Regards, JD

2 1

IPC problem
by Michael Scheibel 16 Feb '07

16 Feb '07

Hello L4 hackers, we've encountered a problem with an IPC transmission based on DICE stubs generated from the following interface definition: UInt32 process( [in, size_is(bufferALen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferA, [in] UInt32 bufferALen, [in, size_is(bufferBLen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferB , [in] UInt32 bufferBLen, [out, size_is(*bufferCLen), max_is(MAX_BUFFER_SIZE)] UInt8** bufferC, [out] UInt32* bufferCLen); UInt8 is defined as unsigned char, UInt32 is defined as unsigned long, MAX_BUFFER_SIZE is 1500. We are using dice version 3.1.0 with the command line options -fforce-corba-alloc -nostdinc -P-DL4API_l4v2 and the latest OTC snapshot. In this configuration bufferB is not transmitted correctly but is received as corrupt data on the server side (which is an L4Linux application). Is there anything wrong with our interface definition? Any hints appreciated! Michael -- Sirrix AG security technologies - http://www.sirrix.com Michael Scheibel eMail: m.scheibel(a)sirrix.com Tel +49(234) 610 071-124 Public key on demand. Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 4

small address-space can not be used in em64t mode ?
by coly 14 Feb '07

14 Feb '07

Hi, The transparently flexing user address space method which is called as "small address-space" uses segment to implement the protection for small address sapce. But in em64t or amd64 mode, there is not segment (except FS,GS) exists. So it seems the small address-space method can not be used under 64bit mode. Isn't it ? Thanks in advance. Coly

2 1

Booting L4Linux on Fiasco-UX fails with kernel panic
by Michael Kasper 14 Feb '07

14 Feb '07

Hello L4-Hackers, I try to become familiar with L4Linux on top of Fiasco-UX. Therefor, I've rebuilt the sources as described online. But booting L4Linux with the example drops-rd.rd ramdisk fails with kernel panic. Shortly after the ramdisk is loaded, the boot process halts with the following message: Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye Has anyone a solution for this? Is the ramdisk not accessible by the L4Linux kernel, or do I need explicitly specify an init parameter? Thanks and kind regards, Michael ################################################# Fiasco-UX on Linux 2.6.18-gentoo-r6 (i686) Native Syscall Map: 0x600 Mapped 256 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00099364 [/base/drops/l4/build/bin/x86_586/l4v2/sigma0] Loading Module 0x00120000-0x002b29e4 [/base/drops/l4/build/bin/x86_586/l4v2/roottask] Copying Module 0x0ea5d000-0x0ea847ff [/base/drops/l4/kernel/fiasco/build/Symbols] Copying Module 0x0ea24000-0x0ea5cedc [/base/drops/l4/kernel/fiasco/build/Lines] Copying Module 0x0e9e4000-0x0ea2347e [/base/drops/l4/build/bin/x86_586/l4v2/names] Copying Module 0x0e9a7000-0x0e9e3dc8 [/base/drops/l4/build/bin/x86_586/l4v2/log] Copying Module 0x0e921000-0x0e9a63c7 [/base/drops/l4/build/bin/x86_586/l4v2/dm_phys] Copying Module 0x0e8d6000-0x0e92068d [/base/drops/l4/build/bin/x86_586/l4v2/simple_ts] Copying Module 0x0e822000-0x0e8d5804 [/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov] Copying Module 0x0e7f0000-0x0e821f37 [/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux] Copying Module 0x0e71e000-0x0e7ef395 [/base/drops/l4/build/bin/x86_586/l4v2/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: GenuineIntel (6:F:6:0) Model: Core 2 (Merom) at 2394 MHz 128 Entry I TLB (4K pages) 272 Entry D TLB (4K pages) 48 Entry D TLB (4M pages) 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 4096 KB L2 U Cache (16-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ ea99000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Found Fiasco-UX. Command line found: "/base/drops/l4/build/bin/x86_586/l4v2/roottask -symbols -lines" 261120kB ( 255MB) total RAM (reported by bootloader) 235040kB ( 230MB) received RAM from Sigma0 5488kB ( 6MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 7 modules. #05: loading "/base/drops/l4/build/bin/x86_586/l4v2/names " from [0e9e4000-0ea2347e] to [002d0000-002d5f6a][002d6000-002e2000] entry at 0000d088 via trampoline page code #06: loading "/base/drops/l4/build/bin/x86_586/l4v2/log" from [0e9a7000-0e9e3dc8] to [00400000-004064ca][00407000-004398b0] entry at 0000e084 via trampoline page code #07: loading "/base/drops/l4/build/bin/x86_586/l4v2/dm_phys " from [0e921000-0e9a63c7] to [01500000-0150e50a][0150f000-01519000] entry at 0000f088 via trampoline page code #08: loading "/base/drops/l4/build/bin/x86_586/l4v2/simple_ts " from [0e8d6000-0e92068d] to [01400000-014080ea][01409000-0141b070] entry at 0001008c via trampoline page code #09: loading "/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov" from [0e822000-0e8d5804] to [00500000-0051ec6c][0051f000-00553000] entry at 00011088 via trampoline page code #0a: loading "/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux" from [0e7f0000-0e821f37] to [01080000-01084040][01085000-0108a000] entry at 00012088 via trampoline page code #0b: loading "/base/drops/l4/build/bin/x86_586/l4v2/loader /base/drops/l4/cfg/l4linux26.ux" from [0e71e000-0e7ef395] to [01300000-01320642][01321000-0134c000] entry at 000130a8 via trampoline page code simplets| Configured for 64 tasks. loader | Can't map tbuf status page fuxfprov| File provider started, registered as 9.02 fuxfprov| open "/base/drops/l4/cfg/l4linux26.ux" by B.02 loader | sleeping for 2000 ms fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by B.02 loader | vmlinuz26.ux: Starting application using libld-l4.s.so loader | vmlinuz26.ux,#c: Loading binary fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/libld-l4.s.so" by B.02 loader | vmlinuz26.ux,#c: Loading ldso loader | Capability support not supported. loader | vmlinuz26.ux,#c: Starting libld-l4.s.so at 00013890 via 0000cf00 fuxfprov| open "./libloader.s.so" by C.00 fuxfprov| Can't open "./libloader.s.so": -2 fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/./libloader.s.so" by C.00 fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by C.00 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3 l4lx : .4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local tim l4lx : e zone must be set--see zic man l4lx | Binary name: /base/drops/l4linux-2.6/vmlinuz26.ux l4lx | Kernel command line (7 args): mem=128M root=1:0 load_ramdisk=1 ramdis l4lx : k_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de l4lx | Image: 00400000 - 0054e000 [1336 KiB]. l4lx | Areas: Text: 00400000 - 004cf000 [828kB] (a bit longer) l4lx | Data: 004cf000 - 004eb63c [113kB] l4lx | Initdata: 004ee000 - 00503000 [84kB] l4lx | BSS: 00504000 - 0054cd50 [291kB] l4lx | l4lx_thread_create: Created thread 0c.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0c.04 (server) l4lx | main thread will be 0c.04 l4lx | l4env_register_pointer_section: addr = 004cf000 size = 520192 l4lx | sec-w-init: virt: 0x004cf000 to 0x0054dfff [508 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 520192 Bytes l4lx | sec-w-init: 1: Phys: 0x0127d000 to 0x012f6000, Size: 495616 l4lx | sec-w-init: 2: Phys: 0x01356000 to 0x0135c000, Size: 24576 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Main memory: virt: 0x00800000 to 0x087fffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x09800000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1582 entries). l4lx | l4lx_thread_create: Created thread 0c.05 (timer.i0) Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local time zone must be set--see zic man dm_phys: 0000000000800000 - 0000000008800000 [131072 KiB] (usable) 128MB memory available. Zone PFN ranges: DMA 0 -> 512 Normal 512 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 Allocating PCI resources starting at 10000000 (gap: 08800000:f7800000) Detected 2394.000 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) l4lx_irq_timer_startup(0) timer_irq_thread: Starting timer IRQ thread. l4ser_init_ports l4ser: vkey_irq not set - input disabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 129620k/139264k available (729k kernel code, 1300k reserved, 211k data, 84k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08800000 ( 136 MB) .init : 0x004ee000 - 0x00503000 ( 84 kB) .data : 0x004b670c - 0x004eb63c ( 211 kB) .text : 0x00400000 - 0x004b670c ( 729 kB) Calibrating delay using timer specific routine.. 4680.80 BogoMIPS (lpj=23404042) Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K Compat vDSO mapped to 0040e000. CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz stepping 06 Setting up standard PCI resources fuse init (API version 7.7) L4 serial driver l4ser_init_ports l4ser: vkey_irq not set - input disabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye l4lx | panic: going to sleep forever, bye Time: tsc clocksource has been installed. ############################################### # # L4Linux26.ux # modpath "/base/drops/l4linux-2.6" libpath "/base/drops/l4/build/bin/x86_586/l4v2" sleep 2 task "/base/drops/l4linux-2.6/vmlinuz26.ux" "mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de" allow_cli all_sects_writable priority 0xA0 ############################################### # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/base/drops/l4/build" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 CONFIG_L4_USERPRIV_ONLY=y CONFIG_L4_L4ENV_MEMSIZE=128 CONFIG_L4_TAMED=y # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debugging options # CONFIG_L4_DEBUG=y CONFIG_L4_DEBUG_REGISTER_NAMES=y CONFIG_L4_DEBUG_SEGFAULTS=y CONFIG_L4_DEBUG_STATS=y # CONFIG_L4_DEBUG_IRQ_WHEELS is not set CONFIG_L4_DEBUG_TAMED_COUNT_INTERRUPT_DISABLE=y # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # # # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_UTS_NS is not set # CONFIG_IKCONFIG is not set # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_HOTPLUG is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # # CONFIG_BLOCK is not set # # Processor type and features # # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set CONFIG_COMPAT_VDSO=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # # CONFIG_PCI is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_MISC=m # # Networking # # CONFIG_NET is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_SYS_HYPERVISOR is not set # # Connector - unified userspace <-> kernelspace linker # # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # # Misc devices # # CONFIG_TIFM_CORE is not set # # SCSI device support # # CONFIG_SCSI_NETLINK is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # I2O device support # # # ISDN subsystem # # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # # CONFIG_INPUT is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # # CONFIG_VT is not set # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # # Graphics support # # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # # CONFIG_USB_ARCH_HAS_HCD is not set # CONFIG_USB_ARCH_HAS_OHCI is not set # CONFIG_USB_ARCH_HAS_EHCI is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # # CONFIG_DMA_ENGINE is not set # # DMA Clients # # # DMA Devices # # # File systems # CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Miscellaneous filesystems # # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=14 # CONFIG_DEBUG_BUGVERBOSE is not set # CONFIG_DEBUG_FS is not set # CONFIG_UNWIND_INFO is not set # CONFIG_HEADERS_CHECK is not set CONFIG_EARLY_PRINTK=y # CONFIG_DOUBLEFAULT is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_MANAGER=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set # CONFIG_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_PLIST=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y

2 1

large memory model kernel
by David Shifflett 12 Feb '07

12 Feb '07

Hi, I am looking for a development and run-time environment for an experimental kernel. I want to run large memory model (multiple code and data segments). Can L4 / Fiasco support a segmented architecture? Can it support large memory model code? What file formats (ELF, COFF, LE/LX) does it support? What compiler/linker might work? (I am looking at Open WATCOM) Thanks in advance, dave

2 1

Problem compiling dice
by thbach＠students.uni-mainz.de 12 Feb '07

12 Feb '07

Hi, trying to compile the recent cvs-source I got the following error (both, with bison and byacc), while compiling dice: mv -f .deps/IncludeStatement.Tpo .deps/IncludeStatement.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Exception.o -MD -MP -MF .deps/Exception.Tpo -c -o Exception.o Exception.cpp mv -f .deps/Exception.Tpo .deps/Exception.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Dependency.o -MD -MP -MF .deps/Dependency.Tpo -c -o Dependency.o Dependency.cpp mv -f .deps/Dependency.Tpo .deps/Dependency.Po g++ -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -export-dynamic -o dice main.o Compiler.o CParser.o File.o Object.o Visitor.o version.o CCParser.o CCXXParser.o CDCEParser.o CCORBAParser.o CPreProcess.o IncludeStatement.o Exception.o Dependency.o -L../src/be/l4/v2 -lv2 -L../src/be/l4/v2/amd64 -lv2amd64 -L../src/be/l4/v2/ia32 -lv2ia32 -L../src/be/l4/x0 -lx0 -L../src/be/l4/v4 -lv4 -L../src/be/l4/v4/ia32 -lv4ia32 -L../src/be/l4 -ll4 -L../src/be/sock -lsock -L../src/be/cdr -lcdr -L../src/be -lbe -L../src/parser/dce -ldce -L../src/parser/corba -lcorba -L../src/parser/inc -linc -L../src/parser/gcc-c -lgcc_c -L../src/parser/gcc-cxx -lgcc_cxx -L../src/fe -lfe -lstdc++ -ldl collect2: ld returned 1 exit status make[6]: *** [dice] Fehler 1 make[6]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[5]: *** [all-recursive] Fehler 1 make[5]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[4]: *** [all-recursive] Fehler 1 make[4]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[1]: *** [dice] Fehler 2 make[1]: Leaving directory `/home/knoppix/l4/l4/tool' make: *** [tool] Fehler 2 There was allready someone else having this problem in the mailing-list... Any suggestions? Greets, Vincent

2 4

Compile Error in L4 Environment
by WanKeun Jo 12 Feb '07

12 Feb '07

Hi, I've been using L4 packages and fiasco kernel for ARM platform. At this time, I changed my test bed, and made a new environment for L4. Using the same cross toolchain as before, I succeed to compile l4 packages and l4linux. However, when I tried to make a bootstrap image at "l4/build_user/pkg/bootstrap/server/src", the following error occured. The error doens't occur in the previous machine at all. ========================================================================================== ....omitted... Merging image /fiasco to mod00 cp: omitting directory `/fiasco' Use of uninitialized value in concatenation (.) or string at /home/jowkju/project/Microkernel/Latest/l4/pkg/bootstrap/server/src/build.pl line 198. mod00.extra.s: Assembler messages: mod00.extra.s:7: Warning: partial line at end of file ignored Merging image /home/jowkju/project/Microkernel/Latest/l4/build_user/bin/arm_pxa/l4x0/sigma0 to mod01 ....omitted... ==> Linking bootstrap.image LD_PRELOAD=/home/jowkju/project/Microkernel/Latest/l4/tool/gendep/libgendep.so GENDEP_TARGET=bootstrap.image GENDEP_BINARY=ld arm-linux-gcc -o bootstrap.image startup.o exec.o region.o module.o base_critical.o patch.o loader_mbi.o libc_support.o crt0.o init_kip_arm.o mbi_modules.bin mod00.bin mod01.bin mod02.bin mod03.bin mod04.bin mod05.bin mod06.bin mod07.bin mod08.bin mod09.bin mod10.bin mod11.bin mod12.bin mod13.bin mod14.bin mod15.bin -Ttext=0xa1400000 -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib/arm_pxa/l4x0 -L/home/jowkju/project/Microkernel/Latest/l4/lib/arm_pxa/l4x0 -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib/arm_pxa -L/home/jowkju/project/Microkernel/Latest/l4/lib/arm_pxa -L/home/jowkju/project/Microkernel/Latest/l4/build_user/lib -L/home/jowkju/project/Microkernel/Latest/l4/lib -Tbootstrap.ld -larm_drv-pxa -larm_uart -lcxx_base -lcxx_io -lcxx_io_kdebug -nostdlib -Wl,--nostdlib -ll4util -luc_c /opt/crosstool/gcc-3.4.4-glibc-2.2.5/arm-linux/lib/gcc/arm-linux/3.4.4/libgcc.a -Ttext=0xa1400000 -Wl,--warn-common mod00.bin(.module_info+0x0): undefined reference to `_binary_mod00_start' collect2: ld returned 1 exit status make[2]: *** [bootstrap.image] Error 1 ========================================================================================== To fix up the error, I also tried to use the same versions of the tools, which are thought to be related to the problem - gcc,g++, binutils, make, perl, flex, bison, byacc, automake - as before. But , the error not fixed.. Could you help me to use "l4" with the new machine?? Thank you...

2 1

IO Address Mapping
by WanKeun Jo 31 Jan '07

31 Jan '07

Hi, In the previous "sigma0" version, for IO Address mapping, we can add "static Region_instance< start physical address, size, > name;" and then "memmap.add_region &name)"; makes the region available. But now, sigma0 implementation is changed a lot. How can I make a IO Address Region and then add it to sigma0??

2 1

Compilation of Fiasco-1.2 quits...
by thbach＠students.uni-mainz.de 30 Jan '07

30 Jan '07

Hi, I just tried to compile fiasco-1.2 (from the tar-ball). After doing > cd fiasco-1.2/l4/kernel/fiasco > make BUILDDIR=build > cd build > make It quits the compilation with the following output: ... Making startup.o /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:71: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [222]’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:72: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [256]’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:80: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:81: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:92: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:93: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:94: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:95: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:96: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:97: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:98: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:99: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:100 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:103 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:104 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:105 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:106 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:107 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:108 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:109 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:110 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:111 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:120 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:121 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:122 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:123 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:124 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:125 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:126 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:127 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:128 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:129 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ /home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/src/kern/shared/multiboot.h:132 : warning: ‘packed’ attribute ignored for field of type ‘Unsigned8 [189]’ auto/x86desc.h:34: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:35: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:44: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:45: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:46: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:47: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:54: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:55: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:63: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/x86desc.h:64: warning: ‘packed’ attribute ignored for field of type ‘Unsigned8’ auto/timeout.h:42: error: extra qualification ‘Timeout::’ on member ‘get_first_timeout’ auto/kmem.h: In static member function ‘static volatile Address* Kmem::kernel_esp()’: auto/kmem.h:176: warning: dereferencing type-punned pointer will break strict-aliasing rules auto/kmem_alloc.h: At global scope: auto/kmem_alloc.h:19: error: extra qualification ‘Kmem_alloc::’ on member ‘Kmem_alloc’ auto/thread.h:84: error: extra qualification ‘Thread::’ on member ‘d_taskno’ auto/thread.h:90: error: extra qualification ‘Thread::’ on member ‘d_threadno’ auto/thread.h:129: error: extra qualification ‘Thread::’ on member ‘associate_irq’ auto/thread.h:130: error: extra qualification ‘Thread::’ on member ‘disassociate_irq’ auto/thread.h:140: error: extra qualification ‘Thread::’ on member ‘lookup’ auto/mapdb.h:64: warning: ‘packed’ attribute ignored for field of type ‘Mapping_entry’ make[2]: *** [startup.o] Fehler 1 make[2]: Leaving directory `/home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/build' make[1]: *** [all] Fehler 2 make[1]: Leaving directory `/home/vincent/l4-src/fiasco-1.2/l4/kernel/fiasco/build' make: *** [all] Fehler 2 Does someone know how to fix this? I'm building on Debian etch (gcc version 4.1.2) with an Intel Pentium III.

2 1

L4Env DDE questions
by Igor Shmukler 29 Jan '07

29 Jan '07

Hello, I am working on a research project where we are trying to play with information flow between device drivers, and IO stack in general. We want to be able to break disk and network IO in pieces and glue it together as our needs require. From what I understood while going over KMB slides, it seems like L4Env might be an ideal platform for our experiments. However, I am not sure whether I understand how things work correctly. I was wondering if someone could answer some of my questions, to give me a little head start. When Linux drivers are reused, does everyone of these drivers run in its' own address space? Would "reused DDE" drivers still be isolated from one another? Thank you in advance, igor

2 1

[PATCH] L4Linux Ore fix
by Alexander Warg 29 Jan '07

29 Jan '07

No comment -- Alex

1 0

Problem with syscall 243.
by Jorge Cardona 21 Jan '07

21 Jan '07

Hi. I download form the svn of NICTA all the iguana-project--devel--1.2--version-0, and when it was finished, i type: scons machine=pc99 simulate, i also try with toolsuffix=-3.3 and toolsuffix=-4.0 after a moment of compilation it start to run on qemu an image with l4 kernel, iguana and wombat at the top but get's into an infinite loop of: syscall 243 init:1:e4001 unknown syscall I was searching and found that the problem it get solved building a crosscompiler, but it was on a Red Hat system, I'm using a Debian. Some info about my machine: ii libc5 5.4.46-15 The Linux C library version 5 (run-time libr ii libc6 2.3.6-9 GNU C Library: Shared libraries ii libc6-dev 2.3.6-9 GNU C Library: Development Libraries and Hea ii libc6-i686 2.3.6-9 GNU C Library: Shared libraries [i686 optimi ii libg++2.8.1.3-glibc2.2 2.95.4-27 The GNU C++ extension library - runtime vers ii libstdc++2.10-glibc2.2 2.95.4-27 The GNU stdc++ library $ gcc -print-file-name=libc.so.6 /lib/../lib/libc.so.6 $ gcc -print-file-name=ld-linux.so.2 /lib/../lib/ld-linux.so.2 I'm using Debian on testing. The complete log is: Booting 'L4 NICTA::Iguana' kernel=/boot/grub/kickstart [Multiboot-elf, <0x800000:0x6a98:0x0>, <0x808000:0x0:0x18a8>, shtab=0x80a258 , entry=0x800000] module=/boot/grub/l4kernel [Multiboot-module @ 0x821000, 0x19f295 bytes] module=/boot/grub/ig_server [Multiboot-module @ 0x9c1000, 0x58fde bytes] module=/boot/grub/ig_init [Multiboot-module @ 0xa1a000, 0x55344 bytes] module=/boot/grub/ig_serial [Multiboot-module @ 0xa70000, 0x4dae7 bytes] module=/boot/grub/ig_naming [Multiboot-module @ 0xabe000, 0x41798 bytes] module=/boot/grub/ig_trace [Multiboot-module @ 0xb00000, 0x4104a bytes] module=/boot/grub/ig_timer [Multiboot-module @ 0xb42000, 0x4701e bytes] module=/boot/grub/vmlinux [Multiboot-module @ 0xb8a000, 0x2cbc6c bytes] module=/boot/grub/ramdisk [Multiboot-module @ 0xe56000, 0x7d0000 bytes] module=/boot/grub/startup.script [Multiboot-module @ 0x1626000, 0x1f0 bytes] KickStart 0.13.0 Detected multiboot compliant loader Found an elf32 file called "kernel" located at address 0x00821000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x0000c0 0xf0100200 0x00100200 0x0a4ec 0x0a4ec RWE 0x0010 LOAD 0x00a800 0xf010c000 0x0010c000 0x111e0 0x111e0 RWE 0x0800 LOAD 0x01c000 0x0013e000 0x0013e000 0x0b03c 0x0b03c RWE 0x1000 segment 3 is not loadable, skipping Found an elf32 file called "roottask" located at address 0x009c1000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00150000 0x00150000 0x10032 0x131d0 RWE 0x1000 segment 1 is not loadable, skipping Loaded normal modules.. now the rest Found an elf32 file called "/boot/grub/ig_init" located at address 0x00a1a000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00170000 0x00170000 0x0e032 0x0e090 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_serial" located at address 0x00a70000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00180000 0x00180000 0x0c032 0x0c0a4 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_naming" located at address 0x00abe000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x00190000 0x00190000 0x0a032 0x0a088 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_trace" located at address 0x00b00000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001a0000 0x001a0000 0x0a032 0x0a088 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ig_timer" located at address 0x00b42000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001b0000 0x001b0000 0x0b032 0x0b0ac RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/vmlinux" located at address 0x00b8a000 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x001000 0x001c0000 0x001c0000 0x1ec06c 0x20d0b8 RWE 0x1000 segment 1 is not loadable, skipping Found an elf32 file called "/boot/grub/ramdisk" located at address 0x00e56000 Invalid elf file (-1) Magic is: 00 00 00 00 Found an elf32 file called "/boot/grub/startup.script" located at address 0x0162 6000 Invalid elf file (-1) Magic is: 23 20 49 67 Launching kernel ... NICTA::Pistachio - built on Jan 20 2007 15:57:48 by jorgee@mio using gcc version 3.3.6 (Debian 1:3.3.6-13). Initializing boot memory (f011e000 - f013e000) kmem_init (f011e000, f013e000) [128K] remap area f0100000->00100000 len=3e000, w=1, k=1, size=0 remap area 0013e000->0013e000 len=c000, w=1, k=1, size=0 remap area 00000000->00000000 len=400000, w=1, k=1, size=0 activate_gdt remap area f7000000->07000000 len=1000000, w=1, k=1, size=0 activate_gdt Registering processor 0 in KIP (0MHz, 0MHz) startup_system done domain pairs: (0, 1) Initialising scheduler... Switching to idle thread initial_switch_to:552: Initial switch to: sp = f0113ff8 system has 16 interrupts Initializing root servers root-servers: utcb_area: bf000110 (128KB), kip_area: bff000c0 (4KB) creating root server (000c0001) idle thread started ***************************************** * Iguana system, Copyright 1996-2004 * * ERTOS - National ICT Australia * ***************************************** Unknown type: 258 Iguana init starting Initialise naming: Initialise trace: Initialise timer: Initialise serial: Trace server starting no kernel tracebuffer found Backing memory section: 0x001be000 Backed memory section Driver enable Done driver enable Initial servers started Loading linux wombat is at <0x001c0000:0x003ce000> starting at 0x001c0000 Instance: 0x0500e868 -- server: dc001 objref: 1c0000 Loading eCos Couldn't find: ecos Linux version 2.6.10-i386l4_pc99 (jorgee@mio) (gcc version 4.0.4 20060507 (prere lease) (Debian 4.0.3-3)) #4 Sat Jan 20 16:00:03 COT 2007 Kernel memory ranges: 0: 0x03000000-0x04000000 (4096 pages) total 4096 pages Built 4 zonelists Kernel command line: vmlinux igms_name=ramdisk root=/dev/igms0 PID hash table entries: 128 (order: 7, 2048 bytes) Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 16088k/16400k available (1336k kernel code, 200k reserved, 332k data, 30 0k init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) NET: Registered protocol family 16 PCI: direct init pci_direct_init: calling request_region(0xCF8, 8, "PCI conf1") pci_direct_init: request_region returned 0x0301fe60 calling pci_check_type1() PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: pcibios_fixup_bus : Limiting direct PCI/PCI transfers. PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 Activating ISA DMA hang workarounds. RAM (4096 kB) at 0xxe0000000, Cirrus Logic chipset on PCI bus cirrusfb: Driver for Cirrus Logic based graphic boards, v2.0-pre2 igvfb alloc = 00020000 fb1: Virtual frame buffer device, using 75K of video memory io scheduler noop registered io scheduler anticipatory registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html eth0: RealTek RTL-8029 found at 0xc100, IRQ 10, 52:54:00:12:34:56. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hda: QEMU HARDDISK, ATA DISK drive hda: IRQ probe failed (0xffffffff) hdb: IRQ probe failed (0xffffffff) hdb: IRQ probe failed (0xffffffff) hdc: QEMU CD-ROM, ATAPI CD/DVD-ROM drive hdc: IRQ probe failed (0xffffffff) hdd: IRQ probe failed (0xffffffff) hdd: IRQ probe failed (0xffffffff) elevator: using anticipatory as default io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 88704 sectors (45 MB) w/256KiB Cache, CHS=88/255/63 hda: hda1 hdc: ATAPI 4X CD-ROM drive, 512kB Cache Uniform CD-ROM driver Revision: 3.20 igms0: unknown partition table NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) NET: Registered protocol family 1 NET: Registered protocol family 17 VFS: Mounted root (ext2 filesystem) readonly. syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall syscall 243 init:1:e4001 unknown syscall What can i do to fix this? -- Jorge Eduardo Cardona jorgeecardona(a)gmail.com ------------------------------------------------ Linux registered user #391186 Registered machine #291871 ------------------------------------------------

1 0

GRUB and modaddr
by Manuel A. Fernandez Montecelo 17 Jan '07

17 Jan '07

Hello, If I understood it correctly (stumbling upon a memory overlapping error and searching the web), that 'modaddr' command (or similar name, don't have it around now) exists only in a fork of GRUB maintained to boot Fiasco (and maybe other Dresden/L4 projects). Is there a way to run Fiasco with standard GRUB, or any ongoing work to be able to do it? Regards. -- Manuel A. Fernandez Montecelo <manuel.montezelo(a)gmail.com>

5 6

Fiasco lazy-scheduling question
by eschierb＠sci.kun.nl 17 Jan '07

17 Jan '07

Hi, I'm Erik Schierboom and I study at the Radboud University Nijmegen. Right now, I'm writing my master thesis, under supervision of Hendrik Tews, on the formal verification of a part of Fiasco's IPC implementation. I studied the thesis by René Reusner but I don't fully grasp the lazy-scheduling details. I have the following questions. For one, the description says that the sender is not removed from the ready-list when the switch is made to the receiver (even though it is now in waiting status). However, as the sender is the active thread it is not part of the ready-list by definition (at least that is how I interpreted the system), so how could it be removed anyway? Secondly, the switching from sender to receiver is simply an execution context switch. If the receiver finishes before the sender's time is up, does the receiver switch the execution context back to that of the sender? With regards, Erik

2 1

Re: some problems of when compiling IDL with dice tools
by Ronald Aigner 17 Jan '07

17 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CC'd to l4-hackers, so the most probable solution is in the archives :) chenggh wrote on 17.01.2007 12:04 this: > On Wednesday 17 January 2007 17:04, you wrote: >> chenggh wrote on 17.01.2007 04:52 this: >>> Hi: >>> In the idl file i defined an interface including a function declaration >>> like this: >>> int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); >>> >>> My aim is to define a method which includes a function pointer I define >>> the function name and function parameters by myself. But when I compile >>> there is error. >> Naturally. >> >>> I checked out the dice manual there is nothing about how to deal with >>> function pointer in idl file. Is this style supported by dice IDL ? If >>> it supports how could I do? >> No, don't do it! >> >> Dice is an IDL compiler. IDL stands for Interface Definition Language. >> And IDL is *NOT* the C programming language. Even though IDL looks >> similar to C it is not C. So using function pointers as arguments in an >> interface definition won't work. > > If I want to define a method including a function as a parameter in IDL file > how can I do? You will have to find another way of expressing a call-back function, e.g., using addresses which you convert into a function pointer wherever you want to invoke the function. You could write something like: int foo([in] arg1, [in] unsigned long * addr_func, [in] arg2); (unsigned long* is used here as the type describing a memory location) and then in the component function: /* I did not test this. Maybe it compiles and works, maybe it doesn't. */ foo_component(arg1, unsigned long * addr_func, arg2) { void *(*start_routine)(void*) = addr_func; ... start_routine(...); ... } However, you usually use IDL to describe an interface for a service that runs in a *different* address space. Sending a pointer to a function to that server is useless, because it has no access to that function located in the client's address space. Then again, if the function is located in a shared memory region you could do the above, but would have to "translate" the address from the client's address space location to the server's address space location. Or client and server are located in the same address space. Then you could use the method described above. Greetings, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFrg9m2sAx3Dtx9+YRApzmAJ92VK5ke3N1wfsLD7Aktp8cVhiR/QCggnS5 DU9EjVEN9u4A+bF9G6b7fSs= =9Noj -----END PGP SIGNATURE-----

1 0

Re: some problems of when compiling IDL with dice tools
by Bjoern Doebel 17 Jan '07

17 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 chenggh wrote: > On Wednesday 17 January 2007 15:44, you wrote: >> chenggh wrote: >>> Hi: >>> In the idl file i defined an interface including a function declaration >>> like this: >>> int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); >>> >>> My aim is to define a method which includes a function pointer I define >>> the function name and function parameters by myself. But when I compile >>> there is error. >>> >>> I checked out the dice manual there is nothing about how to deal with >>> function pointer in idl file. Is this style supported by dice IDL ? If >>> it supports how could I do? >> What exactly are you trying to do? > I try to encapsulate the pthread function with some l4 thread functions. In > Linux the pthread definition is like this: > int pthread_create (pthread_t *__restrict __threadp, > __const pthread_attr_t *__restrict __attr, > void *(*__start_routine) (void *), > void *__restrict __arg) __THROW; > So in IDL file I define the similar style but compilation has some errors. > Maybe I must consider other solutions. Why do you need an IDL interface for starting a thread? Can't this just be implemented as a C function? You can have a look at l4/pkg/thread to see how the L4 thread library is implemented. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrgu/P5ijxgQLUNkRAjUNAJ4h4VwnevgtTlxTXnYaz2s7/SwHoACfRjmj ExnO96FlWr/PL7I0fDYNRa8= =9dYs -----END PGP SIGNATURE-----

1 0

some problems of when compiling IDL with dice tools
by chenggh 17 Jan '07

17 Jan '07

Hi: In the idl file i defined an interface including a function declaration like this: int foo([in] arg1, [in] void *( * start_routine)(void *), [in] arg2); My aim is to define a method which includes a function pointer I define the function name and function parameters by myself. But when I compile there is error. I checked out the dice manual there is nothing about how to deal with function pointer in idl file. Is this style supported by dice IDL ? If it supports how could I do? Thanks. cheng

3 2

arm instruction version
by WanKeun Jo 17 Jan '07

17 Jan '07

Hi, In the l4linux-2.6, if set L4ARCH=arm, the processor type is fixed to CPU_SA1100. And the arm instruction version is armv4. I want to use arch-dependent code for pxa, so I changed CPU_SA1100 to CPU_XSCALE config and arm instruction set version to armv5te at --------------------------------------------------- $ l4linux-2.6/arch/l4/Makefile CFLAGS += -D__LINUX_ARM_ARCH__=5 -march=armv5te --------------------------------------------------- and found a code, --------------------------------------------------- $ l4linux-2.6/arch/l4/kernel/arch-arm/setup.c unsigned int processor_id = 0x0001f000; /* ARMv4 */ --------------------------------------------------- The processor_id is fixed to ARMv4 value. My question is 001. How processor_id affect the linux?? Should I also change this value to a armv5te value?? 002. If I have to change it, what is the proper value for armv5te?? I can't find the value anywhere. Thank you!!!

2 1

AW: Documentation for L4Linux/L4Env
by Christian, Martin, OPEE45 16 Jan '07

16 Jan '07

Hi Adam! > maybe the KMB lecture slides are somehow helpful. They are a good starting point to understand the principles. However the mapping to the code is still unclear. Wouldn't it be possible to get a student (HiWi) writing some documentation? > You should have some good understanding of Linux internals though Yes. And that's exactly my problem ... :-( > understand what the important code does. First understand what the important code is. > Besides that you can of course ask questions and I can try to answer them. >From your lecture I understand that a new architecture would require mainly changes to the "Lower Half" of L4Linux. But I suppose there are also changes required to the Syscall Interface. However, since I want to port it to another L4 Interface, I'll also have to rewrite a lot more. So I'm tending more to use either the L4Linux-2.4 (where there is no documentation) or Wombat, which at least builds on the L4.X2 API. Anyways, I fear I won't manage to do it within 6 weeks ... :-( Thanks for the help, Martin.

2 1

Re: Please help me to solve this problem of my application
by chenggh 15 Jan '07

15 Jan '07

Hi: Now the compilation is ok. But when I run this application there are some errors. This is my log: Fiasco-UX on Linux 2.6.15-23-386 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096964 [sigma0-ux] Loading Module 0x00120000-0x002bc9c4 [roottask] Copying Module 0x039a1000-0x039e0de8 [names] Copying Module 0x03965000-0x039a06d1 [log] Copying Module 0x038de000-0x03964162 [dm_phys] Copying Module 0x03854000-0x038ddee7 [clock] Copying Module 0x037cc000-0x03853750 [clk] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Mon Aug 28 08:34:51 2006 compiled with gcc 3.4.6 for AMD Athlon CPU: AuthenticAMD (6:8:1:0) Model: Duron (Applebred) at 1602 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 64 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 20kB for maintenance structures. Roottask. Found Fiasco-UX. Command line found: "roottask" 64512kB ( 63MB) total RAM (reported by bootloader) 55080kB ( 54MB) received RAM from Sigma0 3788kB ( 4MB) reserved RAM for RMGR Received no I/O ports Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 5 modules. #05: loading "names" from [039a1000-039e0de8] to [002d0000-002d614a][002d7000-002e3000] entry at 0000d060 via trampoline page code symbols at [039ee000-039f0000] (8kB), lines at [039e8000-039ee000] (24kB) #06: loading "log" from [03965000-039a06d1] to [00400000-00406c6a][00407000-00439850] entry at 0000e05c via trampoline page code symbols at [039e6000-039e8000] (8kB), lines at [039e0000-039e6000] (24kB) #07: loading "dm_phys" from [038de000-03964162] to [01500000-01511d6a][01512000-0151c000] entry at 0000f060 via trampoline page code symbols at [039db000-039e0000] (20kB), lines at [039ce000-039db000] (52kB) #08: loading "clock" from [03854000-038ddee7] to [01800000-01812bb4][01813000-01833000] entry at 00010060 via trampoline page code symbols at [039ca000-039ce000] (16kB), lines at [039ba000-039ca000] (64kB) #09: loading "clk" from [037cc000-03853750] to [01100000-011124d4][01113000-01133000] entry at 0001105c via trampoline page code symbols at [039b6000-039ba000] (16kB), lines at [039a7000-039b6000] (60kB) clock_s | L4RM: [PF] write at 0x00000000, ip 018001ac, src 8.02 clock_s | [8.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): clock_s | unhandled page fault The attachment is the source code, too. Thank you. cheng

2 1

Please help me to solve this problem of my application
by chenggh 13 Jan '07

13 Jan '07

Hi: I write a simple service for L4/Fiasco which encapsulate two methods. clock_gettime() and clock_nanosleep(). Of course now it doesn't not have full functions of these two methods. But when I compile the client application for this server. It has some errors like this: PWD=/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2 make -C /home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2' ==> Linking clk LD_PRELOAD=/home/fiasco/L4.17/l4/tool/gendep/libgendep.so GENDEP_TARGET=clk GENDEP_BINARY=ld gcc -o clk /home/fiasco/L4.17/build/lib/x86_586/crt0.o main.o -Ttext=0x01100000 -L/home/fiasco/L4.17/build/lib/x86_586/l4v2 -L/home/fiasco/L4.17//lib/x86_586/l4v2 -L/home/fiasco/L4.17/build/lib/x86_586 -L/home/fiasco/L4.17//lib/x86_586 -L/home/fiasco/L4.17/build/lib -L/home/fiasco/L4.17//lib -T/home/fiasco/L4.17/build/lib/x86_586/main_stat.ld -lclock -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a -luc_c -ll4sys -Ttext=0x01100000 -Wl,--warn-common -Wl,-gc-sections main.o: In function `main':/home/fiasco/L4.17/l4/pkg/clock/examples/client/main.c:11: undefined reference to `clock_gettime' collect2: ld returned 1 exit status make[1]: *** [clk] Error 1 make[1]: Leaving directory `/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2' make: *** [/home/fiasco/L4.17/build/pkg/clock/examples/client/OBJ-x86_586-l4v2] Error 2 it says there is no declaration of clock_gettime(). But according to the same method as showing in BID tutorial my hello example runs well. There is attachment of all my source code file. Please help me and I have this problem for many days. Thank you. Cheng

2 1

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