l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

l4linux-2.6 compilation: acpi problems: undefined reference *acpi*
by Konstantinos Pachopoulos 11 Jan '06

11 Jan '06

Hi, it seems like there are some acpi problems: ------------------------------------ ..... drivers/built-in.o(.init.text+0x52c0): In function `display_to_var': /usr/src/l4linux/l4linux-2.6/drivers/video/console/fbcon.c:749: undefined refere nce to `acpi_ht' drivers/built-in.o(.init.text+0x52ca):/usr/src/l4linux/l4linux-2.6/drivers/video /console/fbcon.c:750: undefined reference to `acpi_pci_disabled' drivers/built-in.o(.init.text+0x52d4):/usr/src/l4linux/l4linux-2.6/drivers/video /console/fbcon.c:752: undefined reference to `acpi_noirq' drivers/built-in.o(.init.text+0x5b5d): In function `acpi_pci_root_init': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_root.c:347: undefined reference to `acpi_pci_disabled' drivers/built-in.o(.init.text+0x5cc1): In function `irqrouter_init_sysfs': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_link.c: undefined reference to `ac pi_noirq' drivers/built-in.o(.init.text+0x5ced): In function `acpi_pci_link_init': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_link.c: undefined reference to `ac pi_noirq' arch/l4/pci/built-in.o(.text+0x45a): In function `get_base_addr': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/mmconfig.c:27: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.text+0x464):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/m mconfig.c:27: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.text+0x15d3): In function `pcibios_penalize_isa_irq': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1078: undefined reference to `a cpi_noirq' arch/l4/pci/built-in.o(.text+0x164e): In function `pirq_enable_irq': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c: undefined reference to `mp_irq _entries' arch/l4/pci/built-in.o(.text+0x165c):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.text+0x1666):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.text+0x16dd): In function `pcibios_fixup_irqs': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:922: undefined reference to `IO _APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.text+0x1728):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c:932: undefined reference to `IO_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x71d): In function `pci_mmcfg_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/mmconfig.c:124: undefined reference t o `acpi_parse_mcfg' arch/l4/pci/built-in.o(.init.text+0x72a):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/mmconfig.c:125: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.init.text+0x734):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/mmconfig.c:125: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.init.text+0xeb0): In function `pci_acpi_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/acpi.c:40: undefined reference to `ac pi_noirq' arch/l4/pci/built-in.o(.init.text+0xf22): In function `pirq_sis_set': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c: undefined reference to `acpi_i oapic' arch/l4/pci/built-in.o(.init.text+0xf2b):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/irq.c: undefined reference to `print_IO_APIC' arch/l4/pci/built-in.o(.init.text+0x171b): In function `pcibios_fixup_irqs': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:932: undefined reference to `mp _irq_entries' arch/l4/pci/built-in.o(.init.text+0x1727):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:932: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.init.text+0x1730):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:932: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.init.text+0x1760):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:938: undefined reference to `IO_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x17fa): In function `pci_vector_resources': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1168: undefined reference to `I O_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x1957): In function `pcibios_irq_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1048: undefined reference to `m p_irq_entries' arch/l4/pci/built-in.o(.init.text+0x1960):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:1048: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.init.text+0x196a):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:1048: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.init.text+0x1e2f): In function `pcibios_setup': /usr/src/l4linux/l4linux-2.6/include/asm-l4/i386-arch/asm/acpi.h:149: undefined reference to `acpi_noirq' make: *** [.tmp_vmlinux1] Error 1 kastor:/usr/src/l4linux/l4linux-2.6# -------------------------------------- Any ideas? Thanks ___________________________________________________________ NEW Yahoo! Cars - sell your car and browse thousands of new and used cars online! http://uk.cars.yahoo.com/

2 1

grub-0.97 problem
by Der Herr Hofrat 05 Jan '06

05 Jan '06

HI ! Not to far into l4 yet - so this is most likely quite basic. trying to get L4Linux-2.6 to boot from hard disk. To get it to boot the docs say to use the modified grub - first shot was the grub cvs version - but that does not compile with gcc 3.3.6 (looks like it compiles up to gcc 3.2.X only - so next show was the patched grub-0.97 with the diff from ~adam/grub/ (patch < grub-0.97-os.diff) recompiled (./configure, make) and installed it(make install, grub-install /dev/hda) - booting gives me: GNU GRUB version 0.97-os.1 (640K lower / 228288K upper memory) followed by the menu - so I guess it worked. But if I use any of the features (i.e. set VAR := VAL, reference as $(VAL) ) it does not seem to know of these extensions ? the following is a part of my menu.lst: <snip> set P := (hd0,1)/usr/src/l4/l4/bin/x86_586/l4v2/ set C := (hd0,1)/usr/src/l4/cfg set L := (hd0,1)/usr/src/l4/l4linux/ # For booting GNU/Linux title GNU/Linux kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 read-only title The "hello" program kernel $(P)/rmgr -sigma0 module $(P)/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0 module $(P)/sigma0 module $(P)/hello title The "hello2" program kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0 module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/hello <snip> The target "hello" fails with <snip> kernel $(P)/rmgr -sigma0 Error 1: Filename must be either an absolute pathname or blocklist Press any key to continue... <snip> The target "hello2" loads as expected (it fails for other reasons later though) <snip> kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 [Multiboot-elf, <0x100000:0x20e40:0x0>, <0x121e40:0x483c:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comsp eed 115200 -comport 0 [Multiboot-module @ 0x20f000, 0x56ea4 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 [Multiboot-module @ 0x266000, 0x10211 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/hello [Multiboot-module @ 0x277000, 0xa884 bytes] <snip> I'm excluding hardware problems as the demo-CD version works fine - so its something thats wrong in this menu.lst ? I also tried removing the (hd0,1) from the settings as I did not have that in the hardcoded modules - so using: set P := /usr/src/l4/l4/bin/x86_586/l4v2/ but that did not change anything. regarding booting of linux - with all paths absolute due to the above problem: <menu.lst> title L4Linux 2.6 kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 task modname "bmodfs" module module module module module module boot_priority 0xA8 modaddr 0x02000000 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -serial_esc -comspeed 115200 -comport 0 module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/names module /usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0 module /usr/src/l4/l4/bin/x86_586/l4v2/dm_phys module /usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380 module /usr/src/l4/l4/bin/x86_586/l4v2/rtc module /usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq module /usr/src/l4/l4/bin/x86_586/l4v2/bmodfs module /usr/src/l4/l4/bin/x86_586/l4v2/libloader.s.so module /usr/src/l4/cfg/run.bmodfs.cfg module /usr/src/l4/l4/bin/x86_586/l4v2/run module /usr/src/l4/l4linux-2.6/vmlinuz26 module /usr/src/l4/cfg/l4linux26.cfg module /usr/src/l4/l4/bin/x86_586/l4v2/l4exec module /usr/src/l4/l4/bin/x86_586/l4v2/con --l4io module /usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg <snip> I get the following output when booting: <snip> Booting 'L4Linux 2.6 ' kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 -serial -comport=1 task mod name "bmodfs" module module module module module module module task modname "l4 dope" boot_priority 0xA8 [Multiboot-elf, <0x100000:0x20e40:0x0>, <0x121e40:0x483c:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] modaddr 0x02000000 Setting module load address to 0x2000000 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comsp eed 115200 -comport 1 [Multiboot-module @ 0x2000000, 0x56ea4 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 [Multiboot-module @ 0x2057000, 0x10211 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/names [Multiboot-module @ 0x2068000, 0x2ab0e bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0 [Multiboot-module @ 0x2093000, 0x27a40 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/dm_phys [Multiboot-module @ 0x20bb000, 0x622a7 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380 [Multiboot-module @ 0x211e000, 0x2ffac bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/rtc [Multiboot-module @ 0x214e000, 0x2138b bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq [Multiboot-module @ 0x2170000, 0x1da7d1 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/bmodfs [Multiboot-module @ 0x234b000, 0x8f715 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/libloader.s.so [Multiboot-module @ 0x23db000, 0x8ec94 bytes] module /usr/src/l4/cfg/run.bmodfs.cfg [Multiboot-module @ 0x246a000, 0x78 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/run [Multiboot-module @ 0x246b000, 0x51d69 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/con_demo2 [Multiboot-module @ 0x24bd000, 0x8a3eb bytes] module /usr/src/l4/l4linux-2.6/vmlinuz26 [Multiboot-module @ 0x2548000, 0xda1d5a bytes] module /usr/src/l4/cfg/l4linux26.cfg [Multiboot-module @ 0x32ea000, 0x73 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/l4exec [Multiboot-module @ 0x32eb000, 0x103b97 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/con --l4io [Multiboot-module @ 0x33ef000, 0x17531e bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4l inux26.cfg [Multiboot-module @ 0x3565000, 0xcf4e3 bytes] RMGR: Stage1 loading /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 loading kernel /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 kernel at 00001000-003906a4 detected new-style DD-L4(v2)/Fiasco configuring sigma0: 00090000-00096000, start: 00090000 reserve modules memory range: 02057000-036344e4 starting kernel /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 proto=0x101f20 @ 0x0030097c Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Dec 22 23:02:20 2005 compiled with gcc 3.3.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling CPU: AuthenticAMD (6:8:1:0) Model: Duron (Applebred) at 1601 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: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 124kB for maintenance structures. RMGR: Stage2 running on Fiasco bootloader loaded 16 modules at 02068000-036344e4 total RAM size = 228928 KB (reported by bootloader) received 209268 KB RAM from sigma0 816 KB reserved for RMGR My symbols at 0cde3000-0cde6000 (12kB), lines at 0cdd6000-0cde3000 (52kB) received no I/O ports attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 a b c d e f ] RMGR: Parsing the config options of command line. configured task 0x0b: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] WARNING: couldn't find modname l4dope, only storing it's quota configured task 0x15: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:a8 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "/usr/src/l4/l4/bin/x86_586/l4v2/names" from 02068000-02092b0e to [ 00240000-002467d2 00247000-00253000 ] starting at entry 00240000 via trampoline page code 0005916c symbols at 0cdd4000-0cdd6000 (8kB), lines at 0cdcf000-0cdd4000 (20kB) #06: loading "/usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0" from 02093000-020baa40 to [ 00400000-00406d01 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0005a180 symbols at 0cdcd000-0cdcf000 (8kB), lines at 0cdc8000-0cdcd000 (20kB) #07: loading "/usr/src/l4/l4/bin/x86_586/l4v2/dm_phys" from 020bb000-0211d2a7 to [ 01500000-0151239a 01513000-0151a410 ] starting at entry 01500000 via trampoline page code 0005b16c symbols at 0cdc4000-0cdc8000 (16kB), lines at 0cdb8000-0cdc4000 (48kB) #08: loading "/usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380" from 0211e000-0214dfac to [ 01400000-01407ffa 01408000-01413850 ] starting at entry 01400000 via trampoline page code 0005c178 symbols at 0cdb6000-0cdb8000 (8kB), lines at 0cdb0000-0cdb6000 (24kB) #09: loading "/usr/src/l4/l4/bin/x86_586/l4v2/rtc" from 0214e000-0216f38b to [ 01080000-01084b19 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 0005d168 symbols at 0cdae000-0cdb0000 (8kB), lines at 0cdaa000-0cdae000 (16kB) #0a: loading "/usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq" from 02170000-0234a7d1 to [ 00b80000-00ba322b 00ba4000-00bd8000 ] starting at entry 00b80000 via trampoline page code 0005e174 symbols at 0cd73000-0cdaa000 (220kB), lines at 0cd5d000-0cd73000 (88kB) #0b: loading "/usr/src/l4/l4/bin/x86_586/l4v2/bmodfs" from 0234b000-023da715 to [ 01220000-01236d6c 01237000-0123f000 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/liblo [ 023db000-02469c94 ] passing module /usr/src/l4/cfg/run.bmodfs.cfg [ 0246a000-0246a078 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/run [ 0246b000-024bcd69 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/con_d [ 024bd000-025473eb ] passing module /usr/src/l4/l4linux-2.6/vmlinuz26 [ 02548000-032e9d5a ] passing module /usr/src/l4/cfg/l4linux26.cfg [ 032ea000-032ea073 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/l4exe [ 032eb000-033eeb97 ] starting at entry 01220000 via trampoline page code 0005f16c symbols at 0cd58000-0cd5d000 (20kB), lines at 0cd49000-0cd58000 (60kB) #13: loading "/usr/src/l4/l4/bin/x86_586/l4v2/con --l4io" from 033ef000-0356431e to [ 00b00000-00b4efab 00b4f000-00b61000 ] starting at entry 00b00000 via trampoline page code 00060170 symbols at 0cd3b000-0cd49000 (56kB), lines at 0cd0d000-0cd3b000 (184kB) #14: loading "/usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg" from 03565000-036344e3 to [ 01300000-013265cb 01327000-01339000 ] starting at entry 01300000 via trampoline page code 00061198 symbols at 0cd07000-0cd0d000 (24kB), lines at 0ccf2000-0cd07000 (84kB) simplets| Configured for 380 tasks. rtc | Date:04.01.2006 Time:11:00:09 RMGR: task a.00 at 00b99c57 is trying to get page 00100000 allocated by task 7 ---------------------------------------------------------IP: 0011c6c1 --double page fault (4.00) jdb: ^ Return reboots, "k" enters L4 kernel debugger... Rebooting. <snip> Any hint on what I've messed up - also pointers on how to get usable debug infos out of such a situation would be appreciated - I did fine some short l4_install.notes describing setup of hello + L4Linux but they seem to be a bit out of date. My suspicion is that the grub is not correctly patched and thus these problems... thx ! hofrat

2 2

Re: L4Linux (dm_phys?) problem
by Jugwan Eom 29 Dec '05

29 Dec '05

Oh, I had many many many mistake. :( This is the right image.

1 0

Dataspaces mappings for L4Linux
by Julian Grizzard 21 Dec '05

21 Dec '05

All, I'm running Fiasco on i386 with L4Linux 2.6. Is there an easy way to find out where all L4Linux DMphys DS's are mapped in its virtual memory? My goal is to get the entire mapping of DS's to virtual memory location in L4Linux. I am able to get some of these mappings from the dump-l4 example and from data printed out from L4Linux. However, I don't know where all DS's are mapped (e.g. "L4thread stack"...). Here's some specific questions I am trying to answer: 1) Where is "L4RM heap" mapped? 2) Where are "syms vmlinux" and "lines vmlinux" mapped? 3) Where is "L4thread TCB table" mapped? 4) Where are the "L4thread stack" DS's mapped? 5) Where is "Ghost page 1" mapped? What is that DS by the way? 6) There seems to be some DS's for L4Linux that are created by the loader and there is also the "L4Linux main memory" DS. Are there any other mappings in L4Linux's virtual memory? Thanks! Julian

2 1

wrong gcc major version "2"- use 3.x for l4io
by Konstantinos Pachopoulos 21 Dec '05

21 Dec '05

Hi, issuing a "make" in /usr/src/l4linux/l4, i end up with this error: ----------------------------------------------------- ===Building IDL & includes of "l4io"=== PWD= /usr/src/l4linux/l4/pkg/l4io make -C l4io idl make[2]: Entering directory '/usr/src/l4linux/l4/pkg/l4io' Makefile:8: ***Wrong gcc major version "2"- use 3.x for l4io. Stop. make[2]: Leaving directory '/usr/src/l4linux/l4/pkg/l4io' make[1]: ***[l4io.headers] Error 2 make[1]: Leaving directory '/usr/src/l4linux/l4/pkg' make: ***[pkg] Error 2 kastor:/usr/src/l4linux/l4# ----------------------------------------------------- I use gcc-2.95 for this. However, using gcc-3.3, i ended up with exactly the same error. Having problems using byacc, i changed the conf file and now i use bison, without any problems from this point. I am using the latest sources from CVS- downloaded yesterday in fact. Any ideas about the l4io problem? Thanks, Kostas ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

2 1

Is it a problem to use l4env_freebsd - mode?
by Arthur Mielimonka 21 Dec '05

21 Dec '05

Hello, I was told recently that you are currently in the process of dumping oskit in favor of uclibc or dietlibc. For my work, I need the log_net server which only compiles with oskit. So I cannot abandon it. Are they any problems or reasons why one shouldn't use oskit? Is it possilble to use a mixed configuration (e.g. compile log_net with oskit and own packages with dietlibc and use them together)? Thanks, Arthur

6 5

Track Program_Counter(PC)/regs of L4Linux Task
by Julian Grizzard 19 Dec '05

19 Dec '05

All, I am currently running L4Linux2.6.14 on the Fiasco l4v2 microkernel using i386 arch with mostly default configurations. I need the ability to track the program counter and registers of all threads in the L4Linux task. Here's exactly what I would like to be able to do from a monitoring L4 task: -Obtain the PC/regs for the first thread (thread 0) for L4Linux just before the thread executes it's first instruction. It would be nice to make the thread wait for a signal before beginning execution. -Obtain the PC/regs for any additional thread created or any thread moved for L4Linux (i.e. from a l4_thread_ex_regs call) just before that thread executes. Again, it would be nice to make that thread wait for a signal before beginning its execution. -Randomly preemptively obtain the PC/regs for all threads of L4Linux. -Obtain the PC/regs for all threads of L4Linux on demand. -Receive notification of thread exit for all threads of L4Linux. There are a few items that I do not yet fully understand that *may* make matters more difficult: -The setup code executing in libloader.s.so. -Trampoline code There are a few assumptions I am willing to have for initial testing to make the development easier: -Assume Task number of L4Linux is known by the microkernel (i.e. hard code it in). -Assume Task number of monitoring thread is known by the microkernel. As a first crack, I have added some code to the microkernel to print out information on the L4Linux task, to see if that information would be good to transfer to the monitoring task. Below is a summary of things I have tried and results seen: MODIFICATION #1 l4/kernel/fiasco/src/kern/context.cpp Context::schedule() Goal: Track current PC of L4Linux threads ======================= ... /* in the for loop */ Sys_task_new_frame *regs = sys_frame_cast<Sys_task_new_frame>(next_to_run->regs()); L4_uid id = regs->dst(); if (id.task() == 0xC) // hard coded task of L4Linux { unsigned int ip = next_to_run->regs()->ip(); unsigned int sp = next_to_run->regs()->sp(); printf("task: %d.%d @ ip: %08x sp: %08x\n", id.task(), id.lthread(), ip, sp); } ... ======================= Results: task: 12.3 @ ip: 004ccb0b sp: b00fff80 task: 12.3 @ ip: 004cd303 sp: b01fff7c task: 12.4 @ ip: 004cca9d sp: b00fff80 task: 12.5 @ ip: 00402ae6 sp: 00657f50 ======================= Notes: 004ccb0b - right after an 'int 0x30' in timer_irq_thread 004cd303 - right after an 'int 0x30' in irq_thread_hw 004cca9d - right after an 'int 0x30' in timer_irq_thread 00402ae6 - right after an 'int 0x30' in l4x_idle MODIFICATION #2 l4/kernel/fiasco/src/kern/thread-syscall.cpp Thread::sys_task_new() Goal: Track starting PC of main L4Linux thread (i.e. thread 0) ======================= ... /* near tail of for loop, just before return */ if (taskno == 0xC) // hard coded L4Linux task ID { printf("new task: %d @ ip: %08x sp: %08x\n", taskno, regs->ip(), regs->sp()); } ======================= Results: new task: 12 @ ip: 00015ea0 sp: 00008f6c ======================= Notes: 00015ea0 - part of the libloader.s.so code MODIFICATION #3 l4/kernel/fiasco/src/kern/thread-syscall.cpp Thread::sys_thread_ex_regs() Goal: Track PC entry of new L4Linux threads ======================= ... if (!dst->exists()) { unsigned int task_num = dst_id.task(); unsigned int lthread_num = regs->thread(); new_thread = true; check (new (dst_id) Thread (dst_task, dst_id, sched()->prio(), mcp()) == dst); if (taskno == 0xC) { printf("new thread: %d.%d @ ip: %08x sp: %08x\n", task_num, lthread_num, regs->ip(), regs->sp()); } } else { unsigned int task_num = dst_id.task(); unsigned int lthread_num = regs->thread(); if (taskno == 0xC) { printf("modified thread: %d.%d @ ip: %08x sp: %08x\n", task_num, lthread_num, regs->ip(), regs->sp()); } } ... ======================= Results: modified thread: 12.0 @ ip: ffffffff sp: ffffffff modified thread: 12.0 @ ip: ffffffff sp: ffffffff new thread: 12.1 @ ip: 0001ac10 sp: afe00000 new thread: 12.2 @ ip: 0001ac10 sp: aff00000 modified thread: 12.2 @ ip: ffffffff sp: ffffffff new thread: 12.3 @ ip: 0001ac10 sp: 00657ff8 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.4 @ ip: 0001ac10 sp: b0100000 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.5 @ ip: 0001ac10 sp: b0200000 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.6 @ ip: 0001ac10 sp: b0300000 new thread: 12.7 @ ip: 0001ac10 sp: b0400000 ======================= Notes: 0001ac10 - part of the libloader.s.so code ffffffff - not really useful. wrong data perhaps. QUESTIONS: GENERAL QUESTIONS -Is there any easy to delay execution of newly created threads, both new task thread 0 and additional threads? -Is there an easy way to randomly interrupt L4Linux threads to check their PC value? -Do any L4Linux threads exit? MODIFICATION #1 -Seems like threads resume execution right after an interrupt. I don't see threads getting preempted in the middle of servicing a system call, for example. Any ideas why not? Further, is there one thread dedicated to handling system calls? -Is there any better way to track where all the L4Linux threads are? Maybe somewhere else besides the scheduler? Are any other classes/functions helpful to get this information? MODIFICATION #2 -I believe this is working correctly. See anything wrong here? MODIFICATION #3 -I would like to catch all instances of creating new threads for L4Linux. Will this current approach work, or is it not correct? If my implementation is correct: -Why are L4Linux threads getting modified? -Any idea why my ip and sp values are 0xffffffff for modified threads? -Looks like all new threads start at the same place. How would they distinguish from one another in terms of functionality? Is that encoded in their stack (e.g. when they issue a 'ret', they'll return to different locations or maybe arguments to their function are on the stack?) Any other comments you have would also be appreciated. Thanks! Julian

3 7

Postdoc position at Nijmegen (ROBIN project on OS verification)
by Erik Poll 15 Dec '05

15 Dec '05

(Apologies for multiple copies) The SoS (Security of Systems) group at the Radboud University of Nijmegen in the Netherlands has a vacancy for a postdoc for a 2-year period starting February 1 2006. The vacancy is in the EU project ROBIN (Robust Open Infrastructure), which is a joint project in collaboration with TU Dresden (more specifically Hermann Härtig's operating systems group), ST Micro Electronics and Secunet. The goal of the ROBIN project is to develop a robust platform (Operating System kernel) that can host legacy operating systems and their applications, but that is small enough (in the order of 50-100k lines of code) to apply rigorous formal analysis and construction techniques. The kernel of the robust platform will be written in C++ (with very small parts in assembly). The work in Nijmegen concentrates on the formal specification and verification of key security properties of the kernel. The objectives are to develop, evaluate and assess tool-supported formal methods for the specification and verification of low level systems code, especially operating-system kernel source-code. The aim is not a full verification of the kernel, but rather to show a perspective of what can be achieved with formal methods. A starting point for this work is the VFiasco project at TU Dresden. We are looking for candidates with a recent PhD in Computing Science, a strong background in formal methods, and an interest in applying formal methods to low-level system programs, such as operating system kernels. Experience with (interactive) theorem provers, program verification, or static analysis is a pré, as is an interest in security. You'll be collaborating with a second postdoc working on this project in Nijmegen for two years, Hendrik Tews, who'll be joining the SoS group starting February 2006. Pre-tax salary starts at 2625,- euro per month, but can be more depending on experience. For more info, contact Erik Poll <erikpoll(a)cs.ru.nl> or Hendrik Tews <tews(a)tcs.inf.tu-dresden.de>. The ROBIN project proposal is available on request from either Erik or Hendrik. You can apply by sending a letter of motivation and a detailed cv (preferably in PDF format) and contact details of at least two references to Erik Poll <erikpoll(a)cs.ru.nl> by January 2, 2006. Relevant links: - SoS group at Nijmegen: http://www.cs.ru.nl/sos - VFiasco project at Dresden: http://os.inf.tu-dresden.de/vfiasco/

1 0

L4Linux-2.6.14 perfomance question
by Der Herr Hofrat 12 Dec '05

12 Dec '05

HI ! I'm very new to L4Linux so my question might be obvious - anyway did not find anything directly related in the archive. For a start I did a quick performance comparison using lmbench-3.0. This comparison is based on the L4Linux-2.6 running a debina ramdisk lmbench-3.0 vs Linux-2.6.14 running from harddisk (though data files were in tempfs in both cases - so the HD should not really have much of an impact). L4Linux Linux 2.6.14 com lat.: (us) lat_pipe 14.1-14.5 2.0 lat_fifo 13.9-14.6 2.2 lat_unix 19.4-19.5 3.2 lat_sem 3.5 0.6 lat_proc: (us) fork 805-1249 80-82 exec 3124-3784 212-230 shell 9992-9997 2480-2592 tlb: 7,8,32 always 32 bw com: (MB/s) bw_pipe 921-958 1338-1352 bw_unix 429-753 1122-1138 lat mem: oopses under L4Linux - no results bw_mem: (MB/s) bcopy 3856-4066 5056-5080 rdwr 11937-13242 16052 syscall: (us) null 2.4-2.8 0.13 read 2.6-3.3 0.26-0.31 stat 4.4-4.9 0.89 open 6.5-8.1 1.16-1.39 The thing that supprises me is that the performance variation is much higher than on regular linux - in both cases the system was idle except for lmbench running, so I'm excluding any syslog parties or cron jobs fireing at inconvenient times (i.e bandwidth of UNIX sockets has a variance of almost 50% ?). Generally the performance difference is much larger than I would have expected, especially also in areas where I don't quite understand where the u-kenrel can impact the Linux system (i.e. bcopy, memory read-write) Are these values in the usual range or did I screw up fundamentally ? thx ! Prof. Nicholas Mc Guire University of Lanzhou Distributed & Embedded System Lab http://dslab.lzu.edu.cn School of Information Science and Engeneering mcguire(a)lzu.edu.cn Tianshui South Road 222. Lanzhou 730000 .P.R.China Tel:+86-931-8912025 Fax:+86-931-8912022 Lichtensteinstr. 31, Mistelbach A-2130 Austria Tel:+43-2572-201082 Fax:+43-2572-201084

2 1

Compiling fiasco for ARM
by Marko Wolf 07 Dec '05

07 Dec '05

Hi there! I tried to compile your current CVS Fiasco with the SA1100 ARM CPU target with all other options at default. I used the, at www.arm.com officially mentioned, GNU Toolchain for ARM Processors from www.codesourcery.com. Both target platform versions arm-bare-gcc-3.4.4 (target platform bare metal) and arm-linux-gcc-3.4.4 (target platform linux) fail at final linking with the attached error message. Maybe, I'm using the wrong arm-linux-compiler. What am I doing wrong? Are other mandatory configuration settings? What ARM compiler are you using? Best regards Marko ######### with arm-bare-gcc-3.4.4 ########## ==> Linking fiasco.image arm-linux-ld: Warning: size of symbol `__DTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(_ctors.o) arm-linux-ld: Warning: size of symbol `__CTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(_ctors.o) arm-linux-ld: section .excp [c0026000 -> c002697f] overlaps section .bss._ZGVZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026000 -> c0026003] arm-linux-ld: section .bss._ZZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026004 -> c0026027] overlaps section .excp [c0026000 -> c002697f] uart_console.o: In function `uart_console_init_stage1()':uart_console.cc: (.text._Z24uart_console_init_stage1v+0x88): undefined reference to `__aeabi_atexit' kernel_uart.o: In function `Kernel_uart::uart()':kernel_uart.cc: (.text._ZN11Kernel_uart4uartEv+0x3c): undefined reference to `__aeabi_atexit' kernel_console.o: In function `Kconsole::console()':kernel_console.cc: (.text._ZN8Kconsole7consoleEv+0x50): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD1Ev+0xe4): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD2Ev+0xe4): undefined reference to `__aeabi_atexit' mapdb.o:mapdb.cc:(.text._ZN5Mapdb4freeEP7Mapping+0x270): more undefined references to `__aeabi_atexit' follow /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `get_eit_entry':unwind-arm.c:(.text+0x45c): undefined reference to `__exidx_start' :unwind-arm.c:(.text+0x460): undefined reference to `__exidx_end' /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `unwind_phase2':unwind-arm.c:(.text+0x4c8): undefined reference to `abort' /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `__gnu_Unwind_Resume':unwind-arm.c:(.text+0x6f4): undefined reference to `abort' make[3]: *** [fiasco.image] Fehler 1 ######### with arm-linux-gcc-3.4.4 ########## ==> Linking fiasco.image arm-linux-ld: Warning: size of symbol `__CTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_ctors.oS) arm-linux-ld: Warning: size of symbol `__DTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_ctors.oS) arm-linux-ld: section .excp [c0026000 -> c002697f] overlaps section .bss._ZGVZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026000 -> c0026003] arm-linux-ld: section .bss._ZZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026004 -> c0026027] overlaps section .excp [c0026000 -> c002697f] uart_console.o: In function `uart_console_init_stage1()':uart_console.cc: (.text._Z24uart_console_init_stage1v+0x80): undefined reference to `__aeabi_atexit' kernel_uart.o: In function `Kernel_uart::uart()':kernel_uart.cc: (.text._ZN11Kernel_uart4uartEv+0x38): undefined reference to `__aeabi_atexit' kernel_console.o: In function `Kconsole::console()':kernel_console.cc: (.text._ZN8Kconsole7consoleEv+0x4c): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD1Ev+0xd8): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD2Ev+0xd8): undefined reference to `__aeabi_atexit' mapdb.o:mapdb.cc:(.text._ZN5Mapdb4freeEP7Mapping+0x13c): more undefined references to `__aeabi_atexit' follow /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_divdi3.oS): (.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_udivdi3.oS): (.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' make[3]: *** [fiasco.image] Fehler 1

2 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers