- l4-hackers - OS Site

Where is kernel entry code
by Yuxin Ren 26 May '14

26 May '14

Hi, Where is the code around kernel entry, including both l4Re and kernel? What is the register format of system call in Fiasco? Thanks a lot. Best

3 3

Missing library question
by Sören Jonsson 26 May '14

26 May '14

Hello, After an upgrade from VMWare Workstation 7 to 10 and removing my previous debian virtual machine. I am now building L4 and L4Re again. The build of L4 went smoothly, but when I try to build L4Re I get the following error message: === Building package "bootstrap" === ===> Linking bootstrap32.elf /usr/bin/ld skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: error: ld returned 1 exit status make [5]: *** [bootstrap32.elf] Error 1 make [4]: *** [/home/osj/l4re/pkg/bootstrap/server/src/OBJ-amd64_amdfam10] Error 2 make [3]: *** [src] Error 2 make [2]: *** [server] Error 2 make [1]: *** [bootstrap] Error 2 make: *** [pkg] Error 2 I have configured L4 and L4Re to build for an AMD K10 processor using the AMD64 architecture. The build OS is: Debian Linux 7.3.0 Compiler: gcc 4.7.2-5 Best regards, Sören Jonsson Sweden

2 1

About DMA mem and IO Server
by Taeung 23 May '14

23 May '14

Thanks Martin :-) Referencing website link which you give me , I'm trying to secure Ethernet on L4Linux. I've got eth0 and configure ip address, netmask , etc. But if I do 'ping 8.8.8.8' for test, error occur such as 'Error connecting: Network is unreachable'. I suspect that the problem is about DMA mem. As below , there is 'WARNING: phys mmio resource allocation failed' log message.. What is the problem ? May this problem be the reason why network is unreachable ? ======================== ..(omitted).. IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000001000000-0000000fffffff] IO | [00000050000000-000000ffffffff] IO | Loading: config 'rom/imx6q.io' *IO | WARNING: phys mmio resource allocation failed** **IO | <0x1bf18>IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002)** **IO | WARNING: phys mmio resource allocation failed** **IO | <0x1bf18>IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002)* IO | P6Device: l4linux "" IO | P6Device: (noname) "L40009" IO | P6Device: imx6q-fec.dev0 "imx6q-fec.0" IO | <0x14678> IOMEM [00000002188000-0000000218bfff 4000] non-pref (32bit) (align=3fff flags=4002) IO | <0x1be28> IRQ [00000000000096-00000000000096 1] none (32bit) (align=0 flags=4001) IO | P6Device: dmamem "dmamem" IO | <0x1bf18> IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002) ..(omitted).. ======================== I'd appreciate whoever give me hints. - Taeung - On 05/10/2014 06:39 PM, Martin Schröder wrote: > Hi Taeung, > this DMAMEM block is mandatory for devices writing/reading directly > into/from RAM. > > Maybe you'll have a look into another board patchset: > http://fooprotected.wordpress.com/2012/04/12/l4linux-patch-for-mv643xx-ethe… > > > and also here: > https://github.com/Ksys-labs/L4Reap/blob/master/files/gumstix-fb-l4l.io > > > > Best regards, > Martin > > > Am 09.05.2014 19:34, TaeWoong Song schrieb: >> Thanks for your advice ,Martin !! >> >> I understand what you mean. >> So, I'm modify source code according to imx6's single Ethernet. >> >> Up to now, FEC Ethernet Driver has been initialized and eth0 has been >> secured in L4Linux. >> But I didn't succeed it yet. >> >> Do I have to need to get DMAMEM ? >> Or, is it fine that I omit DMAMEM ? >> >> However, your patch has been being very helpful to me. >> I'll continue securing Ethernet in L4 Linux. >> >> - Taeung - >> >> On May 9, 2014, at 10:12 PM, Martin Schröder <mschroeder(a)web.de> wrote: >> >>> Just a short addidion: >>> I just had a short look into the freescale spec: The i.MX6 you are >>> using has only a single Ethernet, my i.MX28 has dual Ethernet. So >>> you can skip everything I wrote abot the second PHY connected to the >>> MDIO bus of the first FEC. And you can also remove all lines related >>> to the Dummy-PHY (your Question 5) and turn CONFIG_FIXED_PHY off. >>> >>> Best regards, >>> Martin >>> >>> >>> Gesendet: Mittwoch, 07. Mai 2014 um 16:57 Uhr >>> Von: "Martin Schröder" <mschroeder(a)web.de> >>> An: Taeung <treeze.taeung(a)gmail.com> >>> Betreff: Re: May I ask you questions about your path? >>> Am 07.05.2014 16:08, schrieb Taeung:> Hi, Martin :-) >>>> >>>> Sorry, I take up your time. >>> >>> no problem :-) >>> >>>> May I ask you questions about your path? >>>> >>>> Question 1. In 'imx28.io' file , what mean 'DMAMEM' and 'new-res >>>> Mmio_ram()' ? >>>> >>>> I know that 'Mmio()' need arguments which are start and end address. >>>> But, I don't know 'Mmio_ram()'. >>> >>> I already answered your question on the list :-) >>> >>> you'll find also another reference in the list-archive: >>> >>> <20111117204103.GC13416(a)os.inf.tu-dresden.de> >>> Am 17.11.2011 21:41, schrieb Adam Lackorzynski:> On Thu Nov 17, 2011 >>> at 12:49:31 +0400, Sartakov A. Vasily wrote: >>>>> So.. >>>>> usb host via ehci uses dma and i have problem in >>>>> pool_alloc_page(mm/dmapool.c): >>>>> dma_alloc_coherent (arhc/l4/mm/) returns 0, cos l4x_dma_mem_alloc >>>>> returns 0 too. >>>> >>>> I guess you need to put some 'dmamem' onto your vbus: >>>> >>>> DMAMEM => new Device() >>>> { >>>> .hid = "dmamem"; >>>> new-res Mmio_ram(<size-in-bytes>, 0); >>>> } >>>> >>>> >>>> >>>> Adam >>>> >>> >>>> Question 2. What is namespace 'shmns' ? >>>> >>>> local shmns = loader:create_namespace({shmns = "shmns"}); (line 69) >>>> shmns = shmns:mode("rw"), (line 89) >>>> >>> >>> I am using the l4shmnet network driver to connect two l4linux >>> instances by a virtual network. This driver is based on shared >>> memory, which I assign to both instaces. You'll see the other >>> reference in the linux kernel command lines where this >>> l4shmnet.add=shmns.add=shmns,maxpart=0x12/0x14 is added. >>> >>> >>>> Question 3. In fec_main.c , '#define clk_get_rate(x) 151000000' (line >>>> 312, 349) >>>> How do you know '151000000' ? >>>> Do you found in imx28 data sheet or other document ? >>> >>> I calculated it backwards. In fec_main.c you'll find "Seet MII speed >>> to 2.5 Mhz (= clk_get_rate() / 2 * phy speed)". So I grabbed the >>> divisor (read out the memory in U-Boot) and multiplied it >>> accordingly to get those 2.5 Mhz. But you could also insert some >>> kdebug("%d\n",clk_get_rate()), compile for a native linux and insert >>> this value instead :-) >>> >>>> Question 4. At line 323, why every variables is NULL ? >>> I have no L4-support for the clocing distribution (not within the >>> address space of the fec chip). So clocking the fec is done in U-Boot >>> >>>> Question 5. At line 260, what mean '.link' and '.speed', .duplex ? >>> I set up a virtual "dummy" phy on the second FEC device if this is >>> in another L4 than the first FEC. So this phy should always report >>> "link up", "100 MBit/s" and "full duplex" to the ethernet driver. >>> >>> >>> Martin >>> >> >

3 3

Doing simple I/O in clntsrv example
by Valentin Hauner 22 May '14

22 May '14

Hi! I'm having some trouble with doing simple I/O actions in the clntsrv example (/src/l4/pkg/examples/clntsrv). I want the client to enter minuend and subtrahend himself, so I've added the following code to client.cc: > printf("Please enter minuend and subtrahend: \n"); > l4_uint32_t val1, val2; > std::cin >> val1 >> val2; iostream is included at the beginning of the file. However, the linker has some serious problems: > ==> Linking ex_clntsrv-client > client.o: In function `main': > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::cin' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > client.o: In function `__static_initialization_and_destruction_0': > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::Init()' > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::~Init()' > make[1]: *** [ex_clntsrv-client] Error 1 > make: *** [/home/hnr/l4reb/pkg/examples/clntsrv/OBJ-x86_586-l4f] Error 2 I did not change the Makefile, so g++ is used for compiling (and not gcc). I've added > CXX_FLAGS = -lstdc++ but that doesn't help. I'm using update-alternatives to have different versions of g++ installed simultaneously. Currently, the link points to g++-4.7. But using g++-4.4 does not solve the problem either. Thanks in advance for support!

2 6

interfaces of scheduler Fiasco
by Bouchra Elouri 21 May '14

21 May '14

hello I'm currently reading the code of schudeler fiasco.oc to have an idea about the internal and external interfaces of the scheduler. Can you tell me what exactly are the codes that I have read so I can know the scheduler interfaces (ie with which it communicates) thank you

2 1

Porting Fiasco+L4re to DaVinci DA850 - Linux time wrong
by Peter Howard 21 May '14

21 May '14

I've now got L4Linux running on top of Fiasco+L4re on the DA850. However there appears to be something wrong with the time. Time seems to be passing at a rate of 10-1 (i.e. 1 elapsed second == 10 reported seconds) in Linux. If I change the default Hz rating the L4Linux config (from 100Hz) in either direction L4Linux either hangs or slows down dramatically. If I change the period in the timer driver (in the Fiasco bsp directory) things hang earlier. For the Fiasco BSP I'm using: * timer_tick-single-vector for timer_tick_IMPL, * clock_generic for clock_IMPL, * a da850 timer driver for timer_IMPL. Can someone enlighten me as to how it should work? Thanks -- Peter Howard <pjh(a)northern-ridge.com.au>

2 3

Can you check this patch file(imx6q-fec.patch) ?
by Taeung 20 May '14

20 May '14

Hello, l4 hackers :-) To secure Ethernet on L4 Linux, I've modified source code with yeongchann and we succeeded to obtain Ethernet. we've used 'l4re-snapshot-2014022818' and Freescale i.MX6 Quad SABRE SD board (ARMv7a) I don't know whether this patch can contribute l4 project. But can you check 'imx6q-fec.patch' ? Attached patch is 1. to change UART2 to UART1 for imx6q sabresd (learned by Ahmed Ammar) and 2. to fix compile error(fiasco and l4linux) , 3. to modify source related to FEC ethernet. To put it concretely... ===== About UART for imx6q sabresd ===== (learned by Ahmed Ammar) *1) mem_layout-arm-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp) * 2) uart-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp) * 3) imx.cc* (src/l4/pkg/bootstrap/server/src/platform/imx.cc) ============================== ===== About compile error ===== *1) tb_entry_output.cc* (src/kernel/fiasco/src/kern/tb_entry_output.cc) *2) Kconfig* (src/l4linux/arch/l4/Kconfig) ======================= ** ===== For FEC ethernet ======* **1) mach_setup.c* (src/l4linux/arch/l4/kernel/arch-arm/mach_setup.c) * **2) fec.h* (src/l4linux/drivers/net/ethernet/freescale/fec.h) *3) fec_main.c* (src/l4linux/drivers/net/ethernet/freescale/fec_main.c) *4) fec_ptp.c* (src/l4linux/drivers/net/ethernet/freescale/fec_ptp.c) *5) Kconfig* (src/l4linux/drivers/net/ethernet/freescale/Kconfig) ====================== ===== For access HW on L4Linux ===== *1) imx6q.io* (src/l4/conf/examples/imx6q.io) *2) l4lx-imx6q.cfg* (src/l4/conf/examples/l4lx-imx6q.cfg) * **3) modules.list* (src/l4/conf/modules.list) =========================== I hope this is of some help to someone. - Taeung -

1 0

Fwd: Re: cannot find -lld-l4
by ba_f 18 May '14

18 May '14

Hello Hackers, Am 2014-05-14 11:23, schrieb Matthias Lange: >> /opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-ld: cannot find -lld-l4 >> make[3]: *** [myProg] Fehler 1 > > Have you successfully build the 'ldso' package? libld-l4.so is provided > by > this package. > > Matthias. Yes, the lib seems to be there: obj/l4/arm-ca/lib/arm_armv7a/l4f/libld-l4.so obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/libld-l4.so obj/l4/arm-ca/config/have/ldso.h obj/l4/arm-ca/pc/ldso.pc obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/.ldso.s.o.d objl4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/ldso.s.o I also checked the 2> output from the snapshot build process, which shows a lot of Warnings, but no Error. Am 2014-05-15 01:04, schrieb Adam Lackorzynski: > Are you trying to build a program using shared libraries? Mind to share > your Makefile? Actually, i try to include libssl.a which Ivan Loskutov ported to L4re. http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/005141.html >> BTW before that missing lib error, i get a lot of "multiple definition >> of...". > > Could you show some examples of those errors please? > > Adam ./tpm_integrity.o: In function `TPM_Extend': /home/ba_f/vTPM/server/src/tpm_integrity.c:39: multiple definition of `tpm_log' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:102: first defined here ./tpm_startup.o: In function `TPM_Startup': /home/ba_f/vTPM/server/src/tpm_startup.c:43: multiple definition of `tpm_read_from_storage' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:103: first defined here But these warning/error must come from the build-process, because the code has already been compiled for ARM linux without any Warnings. l4re-snapshot-2014022818 Greets, ba_f

2 1

Doing simple I/O in clntsrv example
by Valentin Hauner 17 May '14

17 May '14

Hi! I'm having some trouble with doing simple I/O actions in the clntsrv example (/src/l4/pkg/examples/clntsrv). I want the client to enter minuend and subtrahend himself, so I've added the following code to client.cc: > printf("Please enter minuend and subtrahend: \n"); > l4_uint32_t val1, val2; > std::cin >> val1 >> val2; iostream is included at the beginning of the file. However, the linker has some serious problems: > ==> Linking ex_clntsrv-client > client.o: In function `main': > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::cin' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > client.o: In function `__static_initialization_and_destruction_0': > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::Init()' > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::~Init()' > make[1]: *** [ex_clntsrv-client] Error 1 > make: *** [/home/hnr/l4reb/pkg/examples/clntsrv/OBJ-x86_586-l4f] Error 2 I did not change the Makefile, so g++ is used for compiling (and not gcc). I've added > CXX_FLAGS = -lstdc++ but that doesn't help. I'm using update-alternatives to have different versions of g++ installed simultaneously. Currently, the link points to g++-4.7. But using g++-4.4 does not solve the problem either. Thanks in advance for support!

3 2

how to get current cpu id
by Yuxin Ren 15 May '14

15 May '14

How can I get the id of cpu(core) the current thread is running on? Thank you

3 3

OKL4 vs L4::Pistachio
by Taylor Bioniks 15 May '14

15 May '14

How does OKL4 compare with L4::Pistachio as far as speed, security, responsiveness? L4::Pistachio uses kickstart to load it, the core kernel is contained in kernel, and the physical memory manager is stored in sigma0, I'm not even sure if it has a virtual memory manager. Does OKL4 have a built in memory manager, and does it handle virtual memory? Thank you.

3 3

Question about dataspace
by Yuxin Ren 15 May '14

15 May '14

I cannot understand dataspace very well. I have some questions about it. Each time I want to alloc a piece of memory, I must create a dataspace first? I look at the example code of memory allocation. I found after create adataspace, we call L4Re::Env::env<http://l4re.org/doc/classL4Re_1_1Env.html#aa1181d6256037deda5b5f83c2006ba60>()->mem_alloc()->alloc() to alloca memory via dataspace. Can I call this function multiple times on the same dataspace instance without free? If so, what is its effect? In addtion we use attach to map the dataspace. Can I attach the same dataspace multiple times without free? In this case, does it mean that the same physical memory is mapped into different virtual address?

2 5

Porting Fiasco+L4re to DaVinci DA850 - prefetch abort in sigma0
by Peter Howard 14 May '14

14 May '14

Dear all, I'm trying to port Fiasco to the DA850. I'm basing this on the 2014022818 snapshot. I've gotten to the point where I've modified the configuration for both fiasco and l4re, added the BSP and bootstrap platform files, and added the extra drivers I need to get started. I can build an image to load on the machine and it boots through the kernel fine. Then it tries to run sigma0 and gets a prefetch abort: EXCEPTION: prefetch abort pfa=c0090100, error=0033000d R[0]: c0002000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 R[8]: 00000000 00000000 00000000 00000000 00000000 c1013de4 04080124 c0090100 (note, I'm including the full boot output at the end of the email) The address, c0090100, is correct as the entry point for sigma0. Now, if I'm reading the FSR right, that's indicating a permission error on the section. But nothing I've added/changed has anything to do with the MMU/mapping. As far as I can see, that's all straight armv5 code, with nothing special to the board (which uses an arm926ejs core). So any idea why sigma0 would be getting mappings with the wrong permission? ------ Full output from boot: U-Boot > bootm 0xc0700000 ## Booting kernel from Legacy Image at c0700000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 860160 Bytes = 840 KiB Load Address: c1000000 Entry Point: c1000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... L4 Bootstrapper Build: #2 Tue May 13 14:38:28 EST 2014, 4.7.3 Scanning up to 32 MB RAM Memory size is 32MB (c0000000 - c1ffffff) RAM: 00000000c0000000 - 00000000c1ffffff: 32768kB Total RAM: 32MB mod04: c10b8000-c10d1574: hello mod03: c109e000-c10b7454: l4re mod02: c106c000-c109d620: moe mod01: c1062000-c106b338: sigma0 mod00: c1015000-c1061380: fiasco Moving up to 5 modules behind c1100000 moving module 00 { c1015000-c106137f } -> { c11bd000-c120937f } [312192] moving module 01 { c1062000-c106b337 } -> { c120a000-c1213337 } [37688] moving module 02 { c106c000-c109d61f } -> { c1214000-c124561f } [202272] moving module 03 { c109e000-c10b7453 } -> { c1100000-c1119453 } [103508] moving module 04 { c10b8000-c10d1573 } -> { c111a000-c1133573 } [103796] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0xc100e000-0xc100e0e2] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0xc0002000 Regions of list 'regions' [ c0001000, c0001a3f] { a40} Kern fiasco [ c0002000, c005afff] { 59000} Kern fiasco [ c0090000, c00965bb] { 65bc} Sigma0 sigma0 [ c0098000, c009e17b] { 617c} Sigma0 sigma0 [ c0140000, c016cb87] { 2cb88} Root moe [ c0170000, c0186f0f] { 16f10} Root moe [ c1000000, c10143f3] { 143f4} Boot bootstrap [ c100a000, c100a0a6] { a7} Boot mbi [ c100e000, c100e1df] { 1e0} Root Multiboot info [ c1014048, c101409f] { 58} Boot mbi [ c1100000, c1133573] { 33574} Root Module API Version: (87) experimental Sigma0 config ip:c0090100 sp:c1013de4 Roottask config ip:c0140260 sp:00000000 Starting kernel fiasco at c0001208 Hello from Startup::stage2 Cache config: ON Timer::Timer() SERIAL ESC: allocated IRQ 61 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned directory compiled with gcc 4.7.3 for Davinci DA850 [] Build: #1 Tue May 13 14:33:35 EST 2014 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 EXCEPTION: prefetch abort pfa=c0090100, error=0033000d R[0]: c0002000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 R[8]: 00000000 00000000 00000000 00000000 00000000 c1013de4 04080124 c0090100 KERNEL: Warning: Sigma0 raised an exception --> HALT Panic: ... Return reboots, "k" enters L4 kernel debugger... -- Peter Howard <pjh(a)northern-ridge.com.au>

2 2

Facing l4x-evict_task problem in L4Linux
by Irvanda Kurniadi 10 May '14

10 May '14

Hi hackers, I want to ask you about my problem in running mpi-program over L4Linux. I'm usinng ubuntu 12.04 kernel with gnu libc-2.15. I put the library from /lib/i386-linux-gnu/ to /lib in my custom ramdisk. Then I put the library that is compiled in the kernel's host to the /usr/lib in my custom ramdisk. I also put my mpi hello program and my own mpi program which are compiled in the kernel's host (I mean in ubuntu 12.04 with libc-2.15). I'm using MPICH3 for the mpi library and I use gforker process manager. When I run the mpi Hello program, it can run properly (I invoke "mpiexec -n 4 ./mpi_hello and there are 4 output from different 4 different processor, it means the program run properly). Then I run my own mpi application which also include the tiff, jpeg, amd libstep libraries that I put altogether in /usr/lib/ in my custom ramdisk. But I got this error message when I invoke "mpiexec -n 1 ./mpi_program image.tif" or "mpiexec -n 2 ./mpi_program image.tif" command (shown below). l4x-evict_tasks: 1089 callbacks suppressed l4x-evict: Found no process to free l4x-evict: Found no process to free l4x-evict: Found no process to free INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=348877 jiffies, g=4294967184, c=4294967183, q=(5) sending NMI to all cpus: and I can't interrupt the running process. I presume this problem happens because the all of process have been finalized but the l4linux kernel still think that there is a remaining process that should be freed. But I'm not sure about this. If you know about this, plis let me know how to fix it and if you can give me an explanation about this I will be really grateful. Thanks, Irvanda

2 1

Re: How to talk to a specific thread in a server
by Björn Döbel 09 May '14

09 May '14

Could you share your client and server's code? Bjoern Am 08.05.2014 21:02, schrieb Yuxin Ren: > Year, > I did those thing. Each server tread has its own server obj and register > server instance, and it calls register_obj() and server.loop() on their own. > But this does not work. And actually the master thread in server always > receives all requests. When I let the master thread to spin, the server > cannot > receive any request, even though other threads in server block on the > server.loop() function. > I am really confused about it. > > Thank you. > > > On Thu, May 8, 2014 at 12:22 PM, Björn Döbel <doebel(a)os.inf.tu-dresden.de>wrote: > > Am Do 08 Mai 2014 18:17:54 CEST schrieb Yuxin Ren: >>>> HiThank you very much for your reply.I did what you said, but the > behavior is very confusing.I create two channels in lua script, and > correspond each channel to a pair of client and server threads. >>>> In the server side, each thread registers its own server obj to its > own Registry_server, and of course they have different dispatch > functions.Now the result is only one server thread receive all requests > from client, and it selects different dispatch function to run based on the > request. >>>> But I want different threads to run different dispatch function, not > only one server thread process all requests using different dispatch > functions.Do you have any ideas about this?Thank you. >>>> On Thu, May 8, 2014 at 2:07 AM, Björn Döbel <doebel(a)os.inf.tu-dresden.de> > wrote: >>>> >>>> ********* *ANFANG des verschlüsselten oder unterschriebenen Bereichs* > ********* >>>> >>>> Hi, >>>> >>>> On 08.05.2014 03:29, Yuxin Ren wrote: >>>>> I have one client and one server talking to each other, and both of >>>>> them have 2 threads. I want thread 1 in client only talk to thread >>>>> 1 in server, and thread 2 in client only talk to thread 2 in >>>>> server. How can I achieve this? >>>> >>>> The simple client/server example >>>> (http://wiki.tudos.org/L4Re_simple_client_server_example) shows how to >>>> connect a single thread in each process (or task in L4 speak). You >>>> could extend this example to create two channels in the Lua setup >>>> file, pass both channels to the tasks during startup and then let each >>>> thread use one of them for communication with its counterpart. >>>> >>>> Note that does not completely enforce your requirement that each >>>> thread can only talk to exactly one other. Capabilities (e.g., for the >>>> communication channels) are shared per task and technically each >>>> thread could therefore send messages on each channel. If you want >>>> strict isolation, you have to separate the threads into separate tasks. >>>> >>>> Bjoern >>>> >>>> >>>> ********* *ENDE des verschlüsselten oder unterschriebenen Bereichs* > ********* >>>> >>>> _______________________________________________ >>>> l4-hackers mailing list >>>> l4-hackers(a)os.inf.tu-dresden.de >>>> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >>>> >>>> >>>> >>>> > > Quick guess: your separate threads need to call the register_obj() > function and the server.loop() functions on their own. (You also need > two independent instances of the Server_object.) > > Bjoern >> >> >

2 1

How to talk to a specific thread in a server
by Yuxin Ren 08 May '14

08 May '14

I have one client and one server talking to each other, and both of them have 2 threads. I want thread 1 in client only talk to thread 1 in server, and thread 2 in client only talk to thread 2 in server. How can I achieve this? Thanks

2 3

Compile library in L4Linux ramdisk
by Irvanda Kurniadi 08 May '14

08 May '14

Hi hackers, Can you help me to check whether my understanding about library in L4Linux is right or wrong? IMO, the library in L4linux ramdisk should be compiled with the same version of compiler. But I found out that every application in l4linux ramdisk is compiled by glibc 2.2.5 for GNU/Linux 2.0.30 which is very old version. Does it mean I have to build the library over that system and then put the built library to the ramdisk of l4linux? Thanks, Irvanda

2 1

What is 'new-res Mmio_ram(0x80000, 0 )' in '.io' file ?
by Taeung 07 May '14

07 May '14

Hi, l4 hackers :-) I'm trying to secure Ethernet on L4 linux using Freescale imx6q. Referencing other 'imx28.io' file which succeeded in securing Ethernet , I'm modifying my 'imx6q.io' file as follows.. =================== hw-root { NIC => new Deviceo() { .hi-d = "imx6q-fec"; new-res Mmio (0x02188000 .. 0x0218BFFF); new-res Irq (150); new-res Irq (151); } DMAMEM => new Deivce() { .hid ="dmamem"; new-res Mmio_ram (0x80000, 0); } 141x => new System_bus() { "imx6q-fec" -> wrap(hw-root.NIC); "dmamem" => wrap(hw-root, DMAMEM); ) } =================== What mean 'DMAMEM' ? And What is the function of which name is 'Mmio_ram()' ? I know that 'Mmio()' need arguments which are start and end address. But, I don't know 'Mmio_ram()'. Please, help me. If you tell a bit me hints, I'd appreciate it. - Taeung -

2 1

How to enable 'CONFIG_COMMON_CLK' ?
by Taeung 30 Apr '14

30 Apr '14

Hello, L4 Hackers :-) I'm trying to build L4 Linux with added option of MMC device driver. When I've tried to compile L4 Linux , I've failed it with error log such as.. ============== drivers/built-in.o: In function `sdhci_pltfm_clk_get_max_clock': /home/taeung/test/source/l4linux/drivers/mmc/host/sdhci-pltfm.c:43: undefined reference to `clk_get_rate' make[1]: *** [vmlinux] Error 1 make: *** [sub-make] Error 2 ============== After I saw the log , I've guessed the cause is that 'drivers/clk/clk.c' was not built. So, I must enable 'CONFIG_COMMON_CLK' , to build 'drivers/clk/clk.c' How to enable 'CONFIG_COMMON_CLK' ? For reference, I've tried to compile L4 Linux with options as follows.. =================================== --- MMC/SD/SDIO card support [ ] MMC debugging [*] Assume MMC/SD cards are non-removable (DANGEROUS) [ ] MMC host clock gating *** MMC/SD/SDIO Card Drivers *** <*> MMC block device driver (8) Number of minors per block device [*] Use bounce buffer for simple hosts < > SDIO UART/GPS class support < > MMC host test driver *** MMC/SD/SDIO Host Controller Drivers *** < > ARM AMBA Multimedia Card Interface support -*- Secure Digital Host Controller Interface support -*- SDHCI platform and OF driver helper <*> Marvell MMP2 SD Host Controller support (PXAV3) < > Marvell PXA9XX SD Host Controller support (PXAV2) < > Synopsys DesignWare Memory Card Interface ==================================== -Taeung -

2 2

L4Linux on amd64 arch
by Irvanda Kurniadi 28 Apr '14

28 Apr '14

Hi hackers, Is there anyone who has tried to build l4linux on amd64? I compiled the new snapshot of L4re, but there is no l4linux for amd64. Can I barely compile this l4linux in l4re-amd64? thanks, Irvanda

2 3

L4linux: cpu and core [comprehension question]
by Irvanda Kurniadi 28 Apr '14

28 Apr '14

Hi hackers, I am a little bit confused about the term of cpu and core in l4linux. I have a system with 8 processor intel xeon E5606 with 4 cores in each cpu. I'm going to maximize it to become the maximum number of cores in all cpus. But I am confused in determining the l4x_cpus that what is the term cpu in here? Is it literally cpu or the number of threads that can be handled in each core? I run an openmp hello world apps over l4linux. I call the omp_get_thread_num() and I got 4 threads in the result. Are these 4 threads obtained from 4 cores in single cpu? So, if I'm right, how can I optimize to use all of the cpu existed in the system? I've tried to use l4x_cpus=8 and l4x_cpus=32, but those commands doesn't work for me. In my opinion, if I can maximize until the maximum number of cores and I have 32 threads that run concurrently, then it will be served by each core in those 8 cpus. In fiasco configuration, there is maximal supported number of CPUs. So referring to my case, the maximum is supposed to be 8, am I right? In case of thread migration in example ex_thread_migrate, I create 16 threads and will be migrated to each cpu. Here is the result: migrate | Migrated Thread00 -> CPU02 migrate | Migrated Thread01 -> CPU03 migrate | Migrated Thread02 -> CPU04 migrate | Migrated Thread03 -> CPU05 migrate | Migrated Thread04 -> CPU06 migrate | Migrated Thread05 -> CPU07 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU01 migrate | Migrated Thread08 -> CPU02 migrate | Migrated Thread09 -> CPU03 migrate | Migrated Thread10 -> CPU04 migrate | Migrated Thread11 -> CPU05 migrate | Migrated Thread12 -> CPU06 migrate | Migrated Thread13 -> CPU07 migrate | Migrated Thread14 -> CPU00 migrate | Migrated Thread15 -> CPU01 My question is do the thread00 and thread08 share the same core in CPU02 or they use different core in CPU02 which run concurrently? And also, is it normal to get the output like cpu[1] to cpu[7] goes to idle loop? Thanks, Irvanda

2 3

Re: L4Linux and L4Re communication
by Björn Döbel 25 Apr '14

25 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25.04.2014 10:24, Irvanda Kurniadi wrote: > On Fri, Apr 25, 2014 at 4:24 PM, Björn Döbel > <doebel(a)os.inf.tu-dresden.de <mailto:doebel@os.inf.tu-dresden.de>> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Hi, > >> In term of running hello world in L4Linux, I can run it by >> passing -m32 -static in the compilation process. But, now I'm >> having a problem in running the mpi-based application on L4Linux >> which this apps needs the mpi library to be able to run. I have >> ported the mpi library and run the apps over L4Re by using Ned. >> So, based on the explanation above, I don't understand how to run >> the mpi-based program on top L4Linux in which the L4Linux >> definitely doesn't have mpi-library because the mpi-library is >> existed in L4Re. Is it like this, the l4linux kernel needs the >> device driver to communicate with external L4 apps (in my case >> mpi-base apps), then to trigger the communication we should make >> the kernel module (linux program to talk to the l4linux kernel). >> Am I right? Can you point one example, which is similar with my >> case, that can be followed by me? > > I see two different scenarios here: > > > 1. Your MPI application is supposed to run as a Linux application > in L4Linux - -> In this case all you need is an MPI library > installed in the Linux distribution that you boot L4Linux into. > E.g., if you are using some custom ramdisk, simply add a (Linux) > MPI library to this disk and your program will then use it. No L4 > magic necessary at all. > > > 2. Your MPI application is supposed to run directly on L4Re - -> In > this case you don't need any Linux or L4Linux in the setup. You > build your L4Re program and link it with your ported MPI library > and then it should run. > > Does that answer your question or am I missing your point? > > > Yes it does. In my case I think I only need to run my application > on L4linux, but since the beginning I misunderstood that I have to > port the library on L4. I have wasted so much time in doing > scenario 2. Sorry to hear that. > What is the differences between running application over L4linux > and running application as a task in L4Re? Good question. Let me try to explain from bottom up. 1. It all starts with Fiasco.OC, our microkernel. Fiasco runs directly on the hardware in the CPU's privileged mode. It provides kernel mechanisms, such as threads, tasks, inter-process communication and scheduling. - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 2. On top of Fiasco.OC we have the L4 Runtime Environment. L4Re is a set of libraries and applications that run in non-privileged (aka "user") mode and implement basic operating system services, such as memory management, device drivers etc. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 3. On top of L4Re you are free to implement your own software using L4Re's and Fiasco's primitives. This is where scenario #2 (MPI on L4Re) comes in. +-----------------+ +---------------------+ | MPI Application | | Another Application | +-----------------+ +---------------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ In contrast to Linux this is a completely different operating system. You mostly don't see that because L4Re provides you with interfaces that are similar to Linux (e.g., a POSIX C library, a virtual file system etc.). With respect to MPI the difference here is that you have to adapt any kind of load balancing, process distribution etc. to use the respective Fiasco and L4Re services. 4. Now we have a special usage scenario: We can slightly adapt the Linux kernel and run it as an application on top of L4Re. This is called L4Linux and the approach is what we call virtualization. +----------------+ | L4Linux Kernel | +----------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 5. A single (L4)Linux kernel does not help you very much, because you want to run applications on top of Linux. Here the virtualization magic steps in and as a result you can run standard Linux applications on top of L4Linux without the need for any modification. Technically, these applications are L4 applications with the difference that their system calls are not sent to the Fiasco kernel but to the L4Linux kernel. The combination of the L4Linux kernel and all Linux applications running on top of it is what we call a virtual machine (VM). Linux VM .............................. . +-------------------+ . . | Linux Application | . . +-------------------+ . . +----------------+ . . | L4Linux Kernel | . . +----------------+ . .............................. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ This setup is how scenario #1 works. Your Linux MPI application believes it is running on a real Linux kernel and Fiasco's virtualization makes sure that everything works as expected. Kind regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNaJo8ACgkQP5ijxgQLUNmSfgCgkQUPRGJ/Vyq0DIQkEi/Dm9+2 gAcAnRdS9hHkIIp9qBYCfHHL1+Uuy2Fi =zFBP -----END PGP SIGNATURE-----

1 0

L4Linux and L4Re communication
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi, This thread is just a sequel from http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006108.html > > Is it possible to run my application on top l4linux; like, > > if I want to run hello world application over l4linux (not just > > booting it over l4/fiasco)? I tried to run it by using this > > configuration: > > > > -- Start Hello loader:start( { caps = {}, l4re_bdg = L4.Dbg.Warn, > > log = {"hello","red"}, }, "rom/hello"); > > > > -- Start Linux loader:start( { caps = { log = L4.Env.log:m("rws"), > > fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = > > vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", > > "yellow" }, }, "rom/" .. lxname .. " mem=64M console=tty0 > > l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 > > ramdisk_size=4000 init=linuxrc"); > > > > But I think it only run two different applications over l4/fiasco. > > > > Do you have any idea how to run the hello application over > > l4linux? > Bjoern said: > > The idea behind L4Linux is to run native Linux applications, so hello > world in L4Linux works just as the version you would write in your > local Linux. > > Running an application that communicates with both L4 and Linux is a > bit more involved. L4Linux applications don't talk to L4 apps > directly. The L4Linux kernel is an L4 app though, so it can do this > talking for you. The missing link then is to write a Linux device > driver that allows your Linux program to talk to the L4Linux kernel, > which then in turn communicates with an external L4 application. > > In term of running hello world in L4Linux, I can run it by passing -m32 -static in the compilation process. But, now I'm having a problem in running the mpi-based application on L4Linux which this apps needs the mpi library to be able to run. I have ported the mpi library and run the apps over L4Re by using Ned. So, based on the explanation above, I don't understand how to run the mpi-based program on top L4Linux in which the L4Linux definitely doesn't have mpi-library because the mpi-library is existed in L4Re. Is it like this, the l4linux kernel needs the device driver to communicate with external L4 apps (in my case mpi-base apps), then to trigger the communication we should make the kernel module (linux program to talk to the l4linux kernel). Am I right? Can you point one example, which is similar with my case, that can be followed by me? Thanks, Irvanda

2 2

build error: [kobject_mapdb.o] error
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi hackers, I have a problem in building l4/fiasco for arm. I'm using ubuntu 11.10 64-bit and want to build l4/fiasco for arm9. For cross compiler, I'm using Sourcery_G++_Lite. For the snapshot, I'm using current snapshot l4re-snapshot-2014022818. Then, when I tried to build the l4/fiasco, I got the error message shown in [1.error message]. Have you ever built l4/fiasco for arm9 over ubuntu 11.10 64-bit? I think this is just a compiler problem. If you know about this problem, please let me know to solve this problem. Thanks, Irvanda [1.error message] make[3]: Entering directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' ... Generating version information ... Making kip.o ... Making kip-debug.o ... Making kip-arm.o ... Making l4_types.o ... Making l4_types-debug.o ... Making l4_fpage.o ... Making l4_msg_item.o ... Making l4_buf_desc.o ... Making l4_error.o ==> Archiving into libabi.a ... Making kernel.arm.lds ... Making crt0.o ... Making bootstrap.o ... Making bootstrap-arm-realview.o ==> Linking bootstrap.fiasco.o ... Making kernel_panic.o ... Making libc_backend_lock.o ... Making cpu_mask.o ... Making rcupdate.o ... Making kobject_mapdb.o In file included from /home/l4re-arm/src/kernel/fiasco/src/kern/context.cpp:22, from /home/l4re-arm/src/kernel/fiasco/src/kern/switch_lock.cpp:85, from /home/l4re-arm/src/kernel/fiasco/src/kern/helping_lock.cpp:4, from /home/l4re-arm/src/kernel/fiasco/src/kern/lock.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject_mapdb.cpp:5, from auto/kobject_mapdb.cc:3: /home/l4re-arm/src/kernel/fiasco/src/lib/libk/cxx/function:34: error: 'cxx::functor<Res(Args ...)>::functor(cxx::functor<Res(Args ...)>&&)' cannot be defaulted make[3]: *** [kobject_mapdb.o] Error 1 make[3]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp'

2 4

Keyboard Input in L4Re Pandaboard ARM
by Erry Pradana Darajati 24 Apr '14

24 Apr '14

Hello L4 hackers I have a question about accessing standard I/O Is it possible to access keyboard using L4Re. If it's possible, can i access it using USB keyboard or do i need to access the std input from serial ? The idea of this question because i want to make a simple calculator to practice study the stdio of L4Re I am really sorry for the basic question And i am appreciating any helps and answer Thanks L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Can you confirm whether or not I secure devices on L4 Linux ?
by Taeung 24 Apr '14

24 Apr '14

Hello, L4 hackers and Wei Jin :-) I'm trying to secure devices which are 'SD card' and 'Ethernet' on L4 Linux. Can you confirm whether or not I secure devices on L4 Linux ? Sorry for long my mail.. The try I've done is as follows .. 1) 'l4lx-vbus.io' file I've modified ==================== # vim:set ft=ioconfig: # configuration file for io l4linux => new System_bus() { NIC => wrap(hw-root.NIC); FLASHMEMORY => wrap(hw-root.FLASHMEMORY); } ==================== 2) 'arm-rv-eb-mc.devs' file I've modified using IRQ and MMIO information in my board's DataSheet . (My board is 'Freescale imx6 Quad SABRE SD') ==================== local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { FLASHMEMORY = Hw.Device { hid = "flashmemory"; Res.mmio(0x02198000 , 0x0219BFFF); Res.irq(56); }, NIC = Hw.Device { hid = "freescale"; Res.mmio(0x02188000, 0x0218BFFF); Res.irq(150); Res.irq(151); }, } ==================== 3) l4lx_xs.cfg I've modified. ==================== local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end loader = L4.default_loader; vbus_l4linux = loader:new_channel(); -- Start io & flash memory loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/arm-rv-eb-mc.devs rom/l4lx-vbus.io"); L4.default_loader:start( { caps = { log = L4.Env.log:m("rws"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M vmalloc=4M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug"); ==================== 4) I've modified 'modules.list' 5) I found something about device on L4 Linux booting log as follows.. ==================== |Starting kernel ... L4 Bootstrapper Build: #8 Tue Apr 22 16:33:35 JST 2014, 4.6.2 20110630 (prerelease) Scanning up to 1024 MB RAM ...(omitted) l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.13.0-l4-svn46 (taeung@taeung-MS-7798) (gcc version 4.6.2 20110630 (prerelease) (Freescale MAD -- Linaro 2011.07 -4 l4linux | Binary name: rom/vmlinuz.arm | ||...(omitted) l4linux | Device scan: l4linux | Device: (noname) l4linux | Device: NIC l4linux | MEM: 02188000 - 0218bfff l4linux | IRQ: 00000096 - 00000096 l4linux | IRQ: 00000097 - 00000097 l4linux | Device: FLASHMEMORY l4linux | MEM: 02198000 - 0219bfff l4linux | IRQ: 00000038 - 00000038 l4linux | Device scan done. || ||||...(omitted) |||DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device '(noname)' with 0 resources. Added static device 'NIC' with 3 resources. Added static device 'FLASHMEMORY' with 2 resources. ...(|||omitted|) mmcblk driver (I've added 'pr_info("|||mmcblk driver|");' in __init function of mmc device driver source code.) ...(|||omitted|)| |mount: mounting /dev/mmcblk0p2 on /mnt failed: No such device or address /etc/init.d/S10getconf: Couldnt mount /dev/mmcblk0p2 Initializing random number generator... random: dd urandom read with 1 bits of entropy available done. Loading libertas firmware... /lib/firmware/libertas not found! /etc/init.d/S30libertas_fw: exit: line 46: Illegal number: -2 Starting network... Cannot find device "usb0" Cannot find device "usb0" Cannot find device "wlan0" Cannot find device "wlan0" Starting dropbear sshd: OK Loading iptables rules... /etc/iptables not found! dnsmasq: unknown interface usb0 Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. Cannot read /proc/net/wireless Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Invalid argument. net.ipv4.ip_forward = 1 / # |==================== I guess that devices is secured through being registered in io server but network could not be run because there is not FEC ethernet driver. (For reference, my board's ethernet use 'FEC Ethernet Driver' ) However I don't know why could not run 'mount /dev/mmcblk0p1 /mnt '. Do I secure devices on L4 Linux successfully ? If I only make drivers for its to run successfully , can I access 'SD card' and 'Ethernet' on L4Linux ? Or is my guess wrong ? I would appreciate if anyone answer. - Taeung -

2 1

Fiasco.OC and qemu vexpress machine model
by Michele Paolino 24 Apr '14

24 Apr '14

Hello l4hackers, I'm trying to execute Fiasco.OC along with the hello module using qemu and the vexpress machine model. For both A9 and A15 cpus the system hangs at "Starting kernel fiasco". It seems that something (the UART driver?) prevents the system to log the kernel boot to the screen. I compiled the image using 'make qemu' in L4RE, and the vm is executed with the argument -nographic. Can you confirm this? Do you have any suggestion to solve it? Here below you can find the log of the A15 boot process: L4 Bootstrapper Build: #2 Thu Apr 10 12:50:53 CEST 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (80000000 - 8fffffff) RAM: 0000000080000000 - 000000008fffffff: 262144kB Total RAM: 256MB mod04: 810bc000-810d5580: hello mod03: 810a2000-810bb460: l4re mod02: 81070000-810a162c: moe mod01: 81066000-8106f344: sigma0 mod00: 81014000-810652e0: fiasco Moving up to 5 modules behind 81100000 moving module 00 { 81014000-810652df } -> { 811c2000-812132df } [332512] moving module 01 { 81066000-8106f343 } -> { 81214000-8121d343 } [37700] moving module 02 { 81070000-810a162b } -> { 8121e000-8124f62b } [202284] moving module 03 { 810a2000-810bb45f } -> { 81100000-8111945f } [103520] moving module 04 { 810bc000-810d557f } -> { 8111a000-8113357f } [103808] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x8100d000-0x8100d0e2] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80001000, 80001cbf] { cc0} Kern fiasco [ 80002000, 8005efff] { 5d000} Kern fiasco [ 80090000, 800963c3] { 63c4} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8016ba6b] { 2ba6c} Root moe [ 80170000, 80186f0f] { 16f10} Root moe [ 81000000, 810133f7] { 133f8} Boot bootstrap [ 81009000, 810090a6] { a7} Boot mbi [ 8100d000, 8100d1df] { 1e0} Root Multiboot info [ 8101304c, 810130a3] { 58} Boot mbi [ 81100000, 8113357f] { 33580} Root Module API Version: (87) experimental Sigma0 config ip:80090100 sp:81012de4 Roottask config ip:801401a0 sp:00000000 Starting kernel fiasco at 800013b0 Regards, Michele Paolino

2 10

L4Linux + Ubuntu
by Sai Prajeeth 23 Apr '14

23 Apr '14

Hi, I want to replace the standard Linux kernel on my Ubuntu Distro (12.04LTS) with the L4Linux kernel. Is this possible? If yes can someone give me an outline as to how to proceed?

5 11

[Resend] Why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ?
by Taeung 23 Apr '14

23 Apr '14

Hi, adam Thank you for answering. :-) Sorry, I've asked you a question with misinformation. I've misunderstood that my Freescale imx6q_sabre_sd board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. My board's Ethernet Controller is contained in imx6 chip. And the driver for it is 'FEC Ethernet Driver'. So, I have to using ethernet driver which is 'l4linux/drivers/net/ethernet/ freescale'. But, I've failed configure 'CONFIG_FEC=y' because there is not 'FEC Ethernet Driver' on L4 linux's build menuconfig. But there are other ethernet drivers which are 'smsc','intel','marvell'... etc. Though there is 'FEC Ethernet Driver' source code in 'l4linux/drivers/net/ethernet/freescale', why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ? How to build FEC ethernet driver for my board? -Taeung- > I'm trying to secure Ethernet environment on L4 Linux. (using > Freescale imx6 > SABRE SD board) > > My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. > > I've found source code for Ethernet Driver. > Folder name is '/l4linux/drivers/net/ethernet/atheros'. > > But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. > I guess 'atheros' driver in L4 Linux don't support my ethernet driver. L4Linux has the same drivers as native Linux, so if the driver is in Linux it is also in L4Linux (in the same version). There seems to be support for this type of network in the imx6 support code. So does the network work with the native Linux of the same version?

2 1

Why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ?
by Taeung 23 Apr '14

23 Apr '14

Hi, adam Thank you for answering. :-) Sorry, I've asked you a question with misinformation. I've misunderstood that my Freescale imx6q_sabre_sd board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. My board's Ethernet Controller is contained in imx6 chip. And the driver for it is 'FEC Ethernet Driver'. So, I have to using ethernet driver which is 'l4linux/drivers/net/ethernet/freescale'. But, I've failed configure 'CONFIG_FEC=y' because there is not 'FEC Ethernet Driver' on L4 linux's build menuconfig. But there are other ethernet drivers which are 'smsc','intel','marvell'... etc. Though there is 'FEC Ethernet Driver' source code in 'l4linux/drivers/net/ethernet/freescale', why 'FEC Ethernet Driver' is not found on L4Linux build menuconfig ? How to build FEC ethernet driver for my board? -Taeung- Message: 3 Date: Wed, 23 Apr 2014 00:17:20 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Can not L4 linux support 'Atheros AR8031-AL1A' Ethernet Driver ? Message-ID: <20140422221720.GC6556(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 On Tue Apr 22, 2014 at 21:55:08 +0900, Taeung wrote: > I'm trying to secure Ethernet environment on L4 Linux. (using Freescale imx6 > SABRE SD board) > > My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. > > I've found source code for Ethernet Driver. > Folder name is '/l4linux/drivers/net/ethernet/atheros'. > > But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. > I guess 'atheros' driver in L4 Linux don't support my ethernet driver. L4Linux has the same drivers as native Linux, so if the driver is in Linux it is also in L4Linux (in the same version). There seems to be support for this type of network in the imx6 support code. So does the network work with the native Linux of the same version? Adam

1 0

Can not L4 linux support 'Atheros AR8031-AL1A' Ethernet Driver ?
by Taeung 23 Apr '14

23 Apr '14

Hello, L4 Hackers :-) I'm trying to secure Ethernet environment on L4 Linux. (using Freescale imx6 SABRE SD board) My board's Ethernet is 'Qualcomm Atheros AR8031-AL1A Gigabit Ethernet'. I've found source code for Ethernet Driver. Folder name is '/l4linux/drivers/net/ethernet/atheros'. But, the folder only contain 'ATL1c' and 'ATL1e', 'ALX', 'ATLX'. I guess 'atheros' driver in L4 Linux don't support my ethernet driver. Is my guess right ? - Taeung -

2 1

Re: Re: How to secure Ethernet environment on L4 Linux ?
by Taeung 21 Apr '14

21 Apr '14

Hello, Adam and L4 Hackers. Thanks for answering. When I run 'ifconfig', nothing have happened. I guess that the cause is /etc folder in ramdisk is not enough to run 'init'. Would you mind if I ask you another question ? Must also I modify 'arm-rv.io' ? or must I modify 'l4lx_xs.cfg' ? or Do not I need do it ? If I have to modify them , how to modify ? (I'm using Freescale imx6q SABRE SD board.) If you give a bit me hints, I'd appreciate. I really want to secure Ethernet on L4 Linux... For reference. I'm using 'entry L4Linux_XS' as follows ======================== entry L4Linux_XS roottask moe rom/l4lx_xs.cfg module l4re module ned module l4lx_xs.cfg module io *module arm-rv.io* module vmlinuz.arm module ramdisk-arm.rd ======================== arm-rv.io in example folder is.. ======================== hw-root { NIC => new Device() { .hid = "smsc911x"; new-res Mmio(0x4e000000 .. 0x4e000fff); new-res Irq(60); } } l4lx => new System_bus() { NIC => wrap(hw-root.NIC); } ======================== l4lx_xs.cfg is .. ======================== -- vim:set ft=lua: local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end L4.default_loader:start( { caps = { log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=/bin/sh"); ======================== - Taeung - Message: 1 Date: Mon, 14 Apr 2014 23:48:27 +0200 From: Adam Lackorzynski<adam(a)os.inf.tu-dresden.de> To:l4-hackers@os.inf.tu-dresden.de Subject: Re: How to secure Ethernet environment on L4 Linux ? Message-ID:<20140414214826.GC6533(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 On Fri Apr 11, 2014 at 10:28:39 +0900, Taeung wrote: > After I succeeded putting other package in ramdisk, I'm trying to take > Ethernet on L4 Linux. > > When I built L4 Linux , I've configured '[*]Network support ' and > '[*]Network device driver support'. > I've copied 'etc' folder from other file system and put it in ramdisk. > And I've put somethings about Network in ramdisk. > > Manually I've mounted '/proc' and '/sys' and tried to run command 'if -a'. > But I've failed secure Ethernet environment on L4 Linux. > To put it concretely, I was not able to run command 'ifup -a' successfully. Does ifconfig show the proper network interface? Adam

2 3

How to change root device on L4 Linux ?
by Taeung 21 Apr '14

21 Apr '14

Hello, L4 hackers :-) I want to change *root device* on L4 Linux instead of ramdisk. Root device I want is like '*/dev/mtdblock0*' or '/dev/mmcblk1p1' instead of 'rom/ramdisk-arm.rd'. So, I've configured somethings in 'L4 Linux menuconfig', additionally. Somethings are as follows .. ============================== <*> MMC/SD/SDIO card support ---> <*> The Extended 4 (ext4) filesystem [*] Ext4 POSIX Access Control Lists [*] Ext4 Security Labels ============================== kernel command line : "rom/vmlinuz.arm console=ttyLv0 root=/dev/mtdblock0 rootwait rw " ============================== But it is hangs at '*Waiting for root device /dev/mtdblock0...*'. I've heard that the solution of this is to pass-through the physical MMC device to L4Linux. Please, tell me it's concrete ways or hints about what I must study for solving this. I can't even guess what the solution mean.. please. - Taeung - ============================== ... vmlinuz.| l4x: Checks passed. vmlinuz.| NetWinder Floating Point Emulator V0.97 (double precision) vmlinuz.| JFS: nTxBlock = 506, nTxLock = 4048 vmlinuz.| msgmni has been set to 126 vmlinuz.| io scheduler noop registered vmlinuz.| io scheduler deadline registered vmlinuz.| io scheduler cfq registered (default) vmlinuz.| L4 serial driver vmlinuz.| ttyLv0 at MMIO 0x1 (irq = 0, base_baud = 230400) is a L4 vmlinuz.| l4ser_shm: L4 shared mem serial driver vmlinuz.| l4cdds: No name given, not starting. vmlinuz.| brd: module loaded vmlinuz.| l4bdds: No name given, not starting. vmlinuz.| mousedev: PS/2 mouse device common for all mice vmlinuz.| TCP: cubic registered vmlinuz.| NET: Registered protocol family 17 *vmlinuz.| Waiting for root device /dev/mtdblock0...* ==============================

3 3

Compiling packages for L4 kernel & patches
by Asus Ceaser 17 Apr '14

17 Apr '14

If I were to use the Fiasco.OC kernel on my Gentoo box, all of my Linux applications will work appropriately without any special tinkering, is this correct. And would I also be able to get packages without having to specially compile them to run on L4. I used to think that if I only had Genode that I would have to specially compile packages, but now for some reason I am unsure. Also since L4 utilizes Linux, all of the Linux patches that are out there would still be able to work for Fiasco.OC, right?

2 1

1 maximal supported CPUs
by Irvanda Kurniadi 16 Apr '14

16 Apr '14

Hi Hackers, I was trying to run ex_thread_migrate in my system. I use 8 active processor. I did config the fiasco to support the multi processor to 8 Maximal supported number of CPUs. Then I ran the thread_migrate example program. After I ran the program, there was only 1 maximal supported CPUs. I even tried to add the -smp 8 while using qemu. But, there wasn't any difference. Please let me know how to fix this. Thanks, Irvanda

2 3

How to secure Ethernet environment on L4 Linux ?
by Taeung 14 Apr '14

14 Apr '14

Hello, l4hackers After I succeeded putting other package in ramdisk, I'm trying to take Ethernet on L4 Linux. When I built L4 Linux , I've configured '[*]Network support ' and '[*]Network device driver support'. I've copied 'etc' folder from other file system and put it in ramdisk. And I've put somethings about Network in ramdisk. Manually I've mounted '/proc' and '/sys' and tried to run command 'if -a'. But I've failed secure Ethernet environment on L4 Linux. To put it concretely, I was not able to run command 'ifup -a' successfully. Please , Help me Even if you tell a bit hints to me, I thank you.

2 1

Ankh Examples
by Ayad Mostafa 09 Apr '14

09 Apr '14

hello l4 hackers, i'm experimenting with ankh and so far failed to successfully ping morpork from my host machine. it seems that receive() blocks at wait_for_data() indefinitely. i can see irq activity on displayed on screen but wait_for_data() does not unblock. i appreciate any help or ideas... software version: l4re revision r63 (2014-02-28) gcc version 4.8.2 qemu version 1.7.0 qemu command: qemu -cpu core2duo -m 128 -cdrom ./morpork.iso \ -net nic,vlan=0,macaddr=00:e0:4c:c6:45:f4,model=rtl8139 -net tap,vlan=0,ifname=tap0 -serial stdio ping command: arping -i tap0 00:E0:4C:C6:45:F4 output: [32mankh | Initialized DDELinux 2.6 [0m [32mankh | <6>net_namespace: 636 bytes [0m [32mankh | Initializing DDE page cache [0m [32mankh | ddekit_pci_init [0m [32mankh | pci bus constructor [0m [32mankh | PCI: L4 root bridge is device 31ca0 [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | l4dde26_register_rx_callback: [36mNew rx callback @ 0x1000200. [0m [0m [32mankh | Softirq daemon starting [0m [32mankh | init_wq_head [0m [32mankh | <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | enable_dev: 0 [0m [32mankh | <6>eth0: RTL-8139C+ at 0x109000, 0x11615cM, IRQ 11 [0m [32mankh | unimplemented: pci_set_master [0m [32mankh | <6>pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de [0m [32mankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI [0m [32mankh | <6>Copyright (c) 1999-2006 Intel Corporation. [0m [32mankh | open_network_devices() [0m [32mankh | opening lo [0m [32mankh | <6>device lo entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | opening eth0 [0m [32mankh | <6>device eth0 entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | Thread 0x85 for IRQ 11 [0m [32mankh | <6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [0m [32mankh | Opened 2 network devices. [0m [32mankh | lo IRQ: 0x00 MAC: 00:00:00:00:00:00 MTU: 16436 [0m [32mankh | eth0 IRQ: 0x0B MAC: 00:E0:4C:C6:45:F4 MTU: 1500 [0m [32mankh | Registered @ registry. [0m [32mankh | Gooood Morning Ankh-Morpoooooork! TID = 0x5a [0m [32mankh | Creating session factory. [0m [32mankh | Configuration: debug,promisc,device=eth0,shm=shm_morpork,bufsize=16384,phys_mac [0m [32mankh | Debug mode ON. [0m [32mankh | Using promiscuous mode. [0m [32mankh | Device 'eth0' requested. [0m [32mankh | SHM area 'shm_morpork' requested. [0m [32mankh | Buffer size: 16384 [0m [32mankh | Physical MAC requested. [0m [32mankh | shmc_create: 0 [0m [32mankh | Created shmc area 'shm_morpork' [0m [32mankh | Assigning MAC address: 00:E0:4C:C6:45:F4 [0m [36mmorpork | Using shm area: 'shm_morpork' [0m [36mmorpork | argv[2] = '16384' [0m [36mmorpork | My TID = 0x93 [0m [36mmorpork | Attached shm area 'shm_morpork': 0 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'tx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9b, TX 9c [0m [36mmorpork | buf @ 0x301c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'rx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9d, TX 9e [0m [36mmorpork | buf @ 0x3074, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | SEND RB @ 0x3018 RECV RB @ 0x3070 INFO @ 0x30c8 [0m [32mankh | l4shmc_attach("shm_morpork") = 0 [0m [32mankh | Shm_chunk::get(0xcf98, "info", 36) [0m [32mankh | ... = 0xcec8 [0m [32mankh | RCV: signal RX 9d, TX 9e [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcd3c, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner 0, name rx_ring, signal rx_signal [0m [32mankh | head @ 0x16c07c, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x16c09d [0m [32mankh | SND: attaching to signal 9e (443000) [0m [32mankh | buf @ 0x16c07c [0m [36mmorpork | activated Ankh connection. [0m [32mankh | xmit thread started, data @ 0xcf38, TID: 0xa0 [0m [32mankh | RCV: signal RX 9b, TX 9c [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcf04, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner ffffffff, name tx_ring, signal tx_signal [0m [32mankh | head @ 0x168030, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x168051 [0m [32mankh | RCV: attaching to signal 9b (448000) [0m [32mankh | 16384 ... 16384 [0m [36mmorpork | RCV: signal RX 9b, TX 9c [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x3114, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | SND: attaching to signal 9c (41c000) [0m [36mmorpork | buf @ 0x103030 [0m [36mmorpork | sender: 0x3100 [0m [36mmorpork | RCV: signal RX 9d, TX 9e [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x317c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | RCV: attaching to signal 9d (41e000) [0m [36mmorpork | receiver: 0x3168 [0m [36mmorpork | Got assigned MAC: 00:E0:4C:C6:45:F4 [0m [36mmorpork | info @ 0x10b0c8 [0m [36mmorpork | 00:E0:4C:C6:45:F4 MTU 1500 [0m [36mmorpork | RX packets: 0 dropped: 0 [0m [36mmorpork | TX packets: 0 dropped: 0 [0m [36mmorpork | RX bytes: 0 TX bytes: 0 [0m [36mmorpork | recv->wait_for_data(); [0m kind regards, ayad

3 8

Ankh Examples
by Ayad Mostafa 08 Apr '14

08 Apr '14

Hi, i also tried it using qemu development branch(version v2.0-rc0), but it is still not working. best regards ayad

1 0

newbie - trying to build
by Jack Andrews 06 Apr '14

06 Apr '14

Hi, Sorry if this is not the right forum. I'm following https://os.inf.tu-dresden.de/fiasco/build.html and i could build fiasco just fine. I made a couple of guesses about how to build L4Re because I couldn't find much info: jack@uv:~/fiasco/src/l4$ mkdir mybuild jack@uv:~/fiasco/src/l4$ make grub2iso E=hello O=mybuild MODULE_SEARCH_PATH=~/fiasco/src/kernel/fiasco/mybuild/ Processing entry 'hello' Could not find 'bootstrap' with path '/home/jack/fiasco/src/kernel/fiasco/mybuild/:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron/l4f:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron/l4f' make: *** [grub2iso] Error 1 I find bootstrap.o, but no 'bootstrap': jack@uv:~/fiasco/src/l4$ find ../kernel/fiasco/mybuild/ -name bootstrap\* ../kernel/fiasco/mybuild/bootstrap.o I have googled, including this list, but I haven't found the magic combination of words to get the answer. Thanks, jack. This is the kernel globalconfig.out: # # Automatically generated file; DO NOT EDIT. # Fiasco configuration # # # Target configuration # # CONFIG_IA32 is not set CONFIG_AMD64=y # CONFIG_ARM is not set CONFIG_PF_PC=y CONFIG_ABI_VF=y CONFIG_AMD64_K8=y # CONFIG_AMD64_CORE2 is not set # CONFIG_AMD64_ATOM is not set # CONFIG_AMD64_K10 is not set # CONFIG_CPU_VIRT is not set CONFIG_SCHED_APIC=y # CONFIG_WORKAROUND_AMD_FPU_LEAK is not set # # Kernel options # CONFIG_MP=y CONFIG_MP_MAX_CPUS=4 CONFIG_CONTEXT_4K=y # CONFIG_FINE_GRAINED_CPUTIME is not set CONFIG_SCHED_FIXED_PRIO=y # CONFIG_SCHED_WFQ is not set # CONFIG_SCHED_FP_WFQ is not set # CONFIG_DISABLE_VIRT_OBJ_SPACE is not set CONFIG_VIRT_OBJ_SPACE=y # # Debugging # # CONFIG_INLINE is not set CONFIG_NDEBUG=y CONFIG_NO_FRAME_PTR=y # CONFIG_STACK_DEPTH is not set # CONFIG_LIST_ALLOC_SANITY is not set # CONFIG_BEFORE_IRET_SANITY is not set # CONFIG_IRQ_SPINNER is not set # CONFIG_WATCHDOG is not set # CONFIG_SERIAL is not set # CONFIG_JDB is not set # CONFIG_POWERSAVE_GETCHAR is not set # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y # CONFIG_WARN_ANY is not set # # Compiling # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_HOST_CC="gcc" CONFIG_HOST_CXX="g++" # CONFIG_MAINTAINER_MODE is not set CONFIG_LABEL="" CONFIG_EXPERIMENTAL=y CONFIG_BIT64=y CONFIG_WARN_LEVEL=1 CONFIG_XARCH="amd64" CONFIG_IA32_TARGET="AMD Opteron" CONFIG_ABI="vf"

4 5

std::cin in Fiasco/L4Re (with 'make qemu')
by Emanuel Berg 03 Apr '14

03 Apr '14

How do I use std::cin in Fiasco/L4Re? The software compiles and links fine, only during execution (with 'make qemu'), this crashes it: Global_Scheduler::Global_Scheduler (bool read_from_file) : period_left(0), number_of_schedulers(0) { if (not read_from_file) { std::cout << "Global scheduler period: "; std::cin >> period; // ... There is no error, but there is no halt to execution (to wait for input), and the value "read" (to period) is inconsistent. -- underground experts united: http://user.it.uu.se/~embe8573

3 8

step forward on compilation
by Emanuel Berg 03 Apr '14

03 Apr '14

First: On - let's see - Fri, 28 Mar 2014 02:02:52 +0100 - I sent a message to this list with the subject "again, must know mechanics of compile" - previously, I was able to send to this list, but as for now, I can't find that message either in the group or in the web archive [1]. (I see my old posts though.) I looked for that message because I thought I build on that thread, that's how I noticed it wasn't there (?). Anyway, as for including header files, I found that you can indeed make a directory at the base package level, called "include" - and put a Makefile in it just like it is done for the other projects (but I'm unsure what the Makefile actually does - perhaps if you specify the include directory as a target in the *package* Makefile, you can drop it?). And, you can't use the C++ ".hh" extension, but ".h" works, if you include them like this: #include <l4/hs/task_scheduler.h> if your package is named "hs". In effect, this is quite the opposite of the #include "task_scheduler.hh", and then the -I flag to the compiler. As for -std=c++11, I found that you can pass that not with CFLAGS, but close - this works: CXXFLAGS += -std=c++11 [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/thread.html -- underground experts united: http://user.it.uu.se/~embe8573

4 9

[Correction] Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello , L4 hackers I'm so sorry.. I amend my a question. Question 'Can't Fiasco.OC support multi-core-processor ?' is wrong.. Again, I've checked my thread and I've tested it. It's problem is about ramdisk or 'dd' command. I guess data in SD-card is some wrong. - Taeung -

1 0

Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello, L4 hackers :-) Always, I'm obliged to you. I have a question. When I configured Fiasco.OC containing option which is 'unable multi processor support' , I've succeeded booting (L4 linux + L4/Fiasco) on Freescale imx6q_sabre_sd(Cortex-a9). And, I've configured Fiasco.OC as follows.. , again. ========================= [*] Enable multi processor support (4) Maximal supported number of CPUs (NEW) [*] Fine-grained CPU time ========================= But I could not booting it successfully. It's stop at '*CPU[3]: goes to idle loop*' What's the problem ? Log I met is such as.... ========================= Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: r62 compiled with gcc 4.6.4 for i.MX6 [] Build: #1 Thu Apr 3 13:48:45 KST 2014 Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) Allocate 2448 bytes (2KB) for CPU[4] local storage (offset=1193508, 0xf11ea000-0xf11ea990) Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) done. Allocate 2448 bytes (2KB) for CPU[1] local storage (offset=1195508, 0xf11ec000-0xf11ec990) MDB: use page size: 20 Cache config: ON ... (ellipsis) MOE: Hello world Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) CPU[1]: goes to idle loop Allocate 2448 bytes (2KB) for CPU[2] local storage (offset=1182508, 0xf11d9000-0xf11d9990) ... (ellipsis) BOOTFS: [11210000Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) -CPU[2]: goes to idle loop 1Allocate 2448 bytes (2KB) for CPU[3] local storage (offset=1158508, 0xf11af000-0xf11af990) 1Cache config: ON 5ID_PFR[01]: 00001231 000000115 ID_[DA]FR0: 00010444 00000000 1ID_MMFR[04]: 00100103 20000000 01230000 00102111 494] [C:508000] vmlinuz.arm BOOTFS: [11552000-11852000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx_xs.cfg MOE: Starting: rom/ned rom/l4lx_xs.cfg MOE: loading 'rom/ned' Ned says: Hi World! L4Re: unhandled exception: pc=0x10211d4 *CPU[3]: goes to idle loop* ========================= - Taeung -

1 0

Custom ramdisk
by Tim Komarov 01 Apr '14

01 Apr '14

Hello, L4 hackers! I use Pandaboard for my practising with Fiasco.OC and L4Linux. 1) I got a problem with booting L4Linux with my own ramdisk. When I use 18 mb ramdisk, I got the following error: reading image.elf 24691072 bytes read ## Starting application at 0x81000000 ... ... ,,,[Everything is usual] ,,, NET: Registered protocol family 17 List of all partitions: No filesystem could mount root, tried: ext3 ext2 ext4 cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.0-l4 #1 [<0200c624>] (unwind_backtrace+0x0/0xec) from [<020054c0>] (show_stack+0x10/0x14) [<020054c0>] (show_stack+0x10/0x14) from [<0222e63c>] (panic+0x7c/0x1b8) [<0222e63c>] (panic+0x7c/0x1b8) from [<022f2c40>] (mount_block_root+0x25c/0x29c) [<022f2c40>] (mount_block_root+0x25c/0x29c) from [<022f2f44>] (prepare_namespace+0x160/0) [<022f2f44>] (prepare_namespace+0x160/0x1b4) from [<022f2894>] (kernel_init_freeable+0x1) [<022f2894>] (kernel_init_freeable+0x174/0x1b8) from [<0222ccf0>] (kernel_init+0x8/0x118) [<0222ccf0>] (kernel_init+0x8/0x118) from [<020077d4>] (ret_from_fork+0x14/0x20) [<020077d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) panic: going to sleep forever, bye To make ramdisk I simply create a file, write 18 Mb of zeroes to it (with dd), create in that file ext2 partition and copy there files from ramdisk-arm.rd So, what should I do to get a proper working ramdisk? 2) Even more. If I create 20 mb ramdisk, I got this: reading image.elf 26788224 bytes read ## Starting application at 0x00000000 ... Than the booting hangs. Why so? Looking forward for your help, guys! Best wishes, Tim

2 3

I share attached this guide with you.
by Taeung 28 Mar '14

28 Mar '14

Hello, l4 hackers :-) !! I've promised a guide Document to you. It is "L4 / Fiasco porting guide on Freescale i.MX6 Quad SABRE SD(ARMv7)". I have had help from L4 Hackers. So, I was able to do booting "L4 Linux + L4/Fiasco.OC" on this board. I'm particularly grateful to /Tim Komarov /and /Ademd Ammar/ , /Adam Lackorzynski/, /Matthias Lange/. I don't know how much this document will help some beginner. I've thought that the guide Document might help them. But I share this document because I have had a big help from them. It is small but I am delighted to be able to contribute this open source community. :-) If it's contents is wrong , let me know your feedback. - Taeung -

3 2

hello/l4/fiasco.oc for realview pbxa9
by Alexis Fajardo Moya 27 Mar '14

27 Mar '14

Hello, recently I tried to run hello program in top of l4/fiasco.oc for exynos 4412 platform, but qemu doest'n have any platform that support it (at least my installed version) none empty machine collie Collie PDA (SA-1110) nuri Samsung NURI board (Exynos4210) smdkc210 Samsung SMDKC210 board (Exynos4210) connex Gumstix Connex (PXA255) verdex Gumstix Verdex (PXA270) highbank Calxeda Highbank (ECX-1000) midway Calxeda Midway (ECX-2000) integratorcp ARM Integrator/CP (ARM926EJ-S) (default) kzm ARM KZM Emulation Baseboard (ARM1136) mainstone Mainstone II (PXA27x) musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) n800 Nokia N800 tablet aka. RX-34 (OMAP2420) n810 Nokia N810 tablet aka. RX-44 (OMAP2420) sx1 Siemens SX1 (OMAP310) V2 sx1-v1 Siemens SX1 (OMAP310) V1 cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) realview-eb ARM RealView Emulation Baseboard (ARM926EJ-S) realview-eb-mpcore ARM RealView Emulation Baseboard (ARM11MPCore) realview-pb-a8 ARM RealView Platform Baseboard for Cortex-A8 realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9 akita Akita PDA (PXA270) spitz Spitz PDA (PXA270) borzoi Borzoi PDA (PXA270) terrier Terrier PDA (PXA270) lm3s811evb Stellaris LM3S811EVB lm3s6965evb Stellaris LM3S6965EVB tosa Tosa PDA (PXA255) versatilepb ARM Versatile/PB (ARM926EJ-S) versatileab ARM Versatile/AB (ARM926EJ-S) vexpress-a9 ARM Versatile Express for Cortex-A9 vexpress-a15 ARM Versatile Express for Cortex-A15 xilinx-zynq-a9 Xilinx Zynq Platform Baseboard for Cortex-A9 z2 Zipit Z2 (PXA27x) For that reason I try to test hello/l4/fiasco.oc in realview pbxa9 platform. I create build directories for l4 and fiasco, configure and compile them for realview pbxa9 platform. Then I execute the following command: ~/build/l4.realview$ make -j2 elfimage E=hello MODULE_SEARCH_PATH=~/build/foc.realview SYSTEM_TARGET=/usr/local/arm-2012.03/bin/arm-none-linux-gnueabi- and this was the result: make[1]: se ingresa al directorio «/home/afmoya/src/l4» =========== Updating RAM_BASE for platform rv_pbx to 0x70000000 ========= ... Regenerating RAM_BASE settings make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ==> Linking sigma0 ==> "sigma0" built ==> Installing sigma0 to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ==> Linking moe ==> "moe" built ==> Installing moe to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Building .general.d ... Building Makefile.inc Building entry "hello". Merging image /home/afmoya/build/foc.realview/fiasco to mod00 [344kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/sigma0 to mod01 [340kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/moe to mod02 [2396kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/l4re to mod03 [1227kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/hello to mod04 [887kB] make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Generating bootstrap.ld ... Compiling exec.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling region.o ... Compiling startup.o ... Compiling init_kip_v2.o ... Compiling init_kip_v4.o ... Compiling libc_support+.o ... Compiling patch.o ... Compiling koptions.o ... Compiling platform/rv.o ... Compiling loader_mbi.o ... Compiling ARCH-arm/reboot.o ==> Linking bootstrap.elf ==> Post-processing bootstrap.elf ==> "bootstrap.elf" built ==> Installing bootstrap.elf in image directory ==> Installing bootstrap.elf to local build-tree ==> Installing bootstrap_hello to local build-tree ==> Installing bootstrap_hello.elf to local build-tree ==> Installing bootstrap_hello in image directory ==> Installing bootstrap_hello.elf in image directory Image size(s) in bytes: bootstrap_hello.elf: 971420 Start address: 0x71000000 --> Build-Nr: 2 make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[1]: se sale del directorio «/home/afmoya/src/l4» After that I execute: ~/build/l4.realview/images$ qemu-system-arm -M realview-pbx-a9 -kernel bootstrap_hello.elf -m 256 -serial mon:stdio -nographic this was the result of the execution: oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory audio: Failed to create voice `lm4549.out' L4 Bootstrapper Build: #2 mié mar 26 13:02:05 CDT 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (70000000 - 7fffffff) RAM: 0000000070000000 - 000000007fffffff: 262144kB Total RAM: 256MB mod04: 710cb000-710e4580: hello mod03: 710b1000-710ca460: l4re mod02: 71077000-710b062c: moe mod01: 7106d000-71076378: sigma0 mod00: 71017000-7106cedc: fiasco Moving up to 5 modules behind 71100000 moving module 00 { 71017000-7106cedb } -> { 711ce000-71223edb } [351964] moving module 03 { 710b1000-710ca45f } -> { 71100000-7111945f } [103520] moving module 04 { 710cb000-710e457f } -> { 71100000-7111957f } [103808] ...and that was all. No "Hello world". After that I kill the qemu process. What 's the problem with my procedure? Sorry for the huge amount of lines of my email. Best regards! Alexis.

2 6

Have you modified L4 Kernel command line ?
by Taeung 27 Mar '14

27 Mar '14

Hello, L4 hackers :-) May I ask you a question about L4 linux ? Have you modified ' l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh' in L4 kernel command ? I want to change it , as if the part of original linux's kernel command line is "root=/dev/mmcblk1p1 rootwait rw" Because I want to assign 'root' to '/dev/mmcblk1p1' or '/dev/mtdblock0' instead of 'rom/ramdisk-arm.rd'. To what I want is achieved, how to modify L4 linux kernel command line ?

2 1

Compiling L4Linux for Pandaboard ARM Error
by Erry Pradana Darajati 25 Mar '14

25 Mar '14

Hello L4 Hackers, i am doing a project that involve L4 and Pandaboard Rev.B1 So far, i am successful to boot Fiasco with L4Re in it. And now, i'm moving on to boot the L4Linux to Pandaboard I'm following the tuts from wiki tudos quickstart. But when i'm try to *make* the L4Linux, it gave me an error like this : =============================================== GEN /media/chiqiVstorage/l4resnap/src/l4linux/TArev2/Makefile CHK include/generated/uapi/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv CC scripts/mod/devicetable-offsets.s gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/empty.o] Error 1 make[3]: *** Waiting for unfinished jobs.... gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/devicetable-offsets.s] Error 1 make[2]: *** [scripts/mod] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [sub-make] Error 2 ================================================================ Is this error caused by my GCC ? i am using GCC from the default repository of ubuntu 13.10 And also, when i'm try to *make mrproper *it gave me error : ERROR: Cannot determine L4 source directory Please properly set the path to your L4 build directory in the configuration menu. But i'm sure i set in the wrong path Is there any solution about my problems above, I am appreciating any help and answer Thank you L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Can use other root file system instead of ramdisk(ramdisk-arm.rd) ?
by Taeung 25 Mar '14

25 Mar '14

Hello , L4 hackers !!:-) Would you mind if I ask you other questions ? I've done booting "L4 linux + L4/Fiasco" on Freescale imx6q_sabre_sd. I'm using ramdisk of which name is 'ramdisk-arm.rd'. I've got the file from URL (os.inf.tu-dresden.de/download/ramdisk-arm.rd). But it is not enough to install and run X-window. There is not enough package. I really want to use 'apt-get' on L4 Linux. 1. Can is what I want possible on L4 linux ? 2. Can use other root file system instead of ramdisk(ramdisk-arm.rd) ? 3. Whatever packages which is put in a ramdisk, is it no matter ? If I put ubuntu packages in a ramdisk, is it fine? - Taeung -

2 1

Is wrong my kernel command line, on this situation ? (Booting L4 linux)
by Taeung 24 Mar '14

24 Mar '14

Hello, every l4-hacker. I've succeeded booting "Hello world + L4/Fiasco" on Freescale i.MX6q_sabre_sd because big help of Admed, Tim, Matthias. And then, I'm trying to boot "L4 Linux + L4/Fiasco" on my board. I've configured for L4 linux build. Such as.. |System type -> ARM system type (L4 Linux) Build type (Use ARMv7) | And then, I've successfully build it. I've did "make uimage E='L4Linux ARM' ..." ,so I've got uimage. And I try to boot it ,using 'uImage' and 'u-boot.bin'. But I did not boot it on my board. It was stoped at "l4linux | panic: going to sleep forever, bye" ==================== ... (eclipsis) Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 Minicom2.6.2RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 112K (022ea000 - 02306000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 CPU: 0 PID: 1 Comm: sh Not tainted 3.13.0-l4-svn46 #1 [<0200b6ec>] (unwind_backtrace+0x0/0xf8) from [<02005308>] (show_stack+0x10/0x14) [<02005308>] (show_stack+0x10/0x14) from [<0222a17c>] (panic+0x78/0x1c0) [<0222a17c>] (panic+0x78/0x1c0) from [<02017d28>] (do_exit+0x724/0x7cc) [<02017d28>] (do_exit+0x724/0x7cc) from [<02017ea0>] (do_group_exit+0x40/0xa0) [<02017ea0>] (do_group_exit+0x40/0xa0) from [<02021754>] (get_signal_to_deliver+0x1a4/0x474) [<02021754>] (get_signal_to_deliver+0x1a4/0x474) from [<02006738>] (do_signal+0x78/0x3d4) [<02006738>] (do_signal+0x78/0x3d4) from [<02006b08>] (do_work_pending+0x74/0xcc) [<02006b08>] (do_work_pending+0x74/0xcc) from [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) from [<00094e9c>] (0x94e9c) panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye ==================== I guess that the problem is somthing about ramdisk(root file system) and kernel command line might be wrong. Referentially I've used ramdisk file(ramdisk-arm.rd) and my kernel command line "setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk1p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'". How do you think about that? Is wrong my kernel command line,on this situation ? - Taeung -

2 1

Re: l4linux
by Taeung 24 Mar '14

24 Mar '14

Hello, Tim I'm glad. Tim Your help save me !!! Thank you very much !!!! :-) I've succeed booting "L4 Linux + L4/Fiasco" on my board(Freescale i.MX6 Quad SABRE SD). After I readjustmy thread for booting, I will write document for booting it on my board. The document might help L4/Fiasco beginner or not, I'll share the document for their. Thank you again !! - Taeung - On 03/24/2014 07:33 PM, Tim Komarov wrote: > Hello, TaeWoong! > I've returned after the weekend. So, my congratulations! I guess that yo don't need my environment anymore :-) > > I suppose that your configuration of L4Linux is wrong. > > Try to build L4Linux like that (arm_defconfig, not your manual configuration): > > $mkdir builddir > > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- arm_defconfig > > Change path to l4re-tree: > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- menuconfig > > Build: > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- -j5 > > It may help you!

1 0

Can you tell me function name that means 'Entry Point: 0x11000000' ?
by Taeung 24 Mar '14

24 Mar '14

Hello, l4 hacker. I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE SD board(Cortex-A9, ARMv7). I'm using 'u-boot' and 'uImage'. So, i build uimage by "make uimage E=hello ~...". And i've try to booting it on Freescale i.MX6q_sabre_sd board. But i did not it because stoped at "Starting kernel ..." !! MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 868352 Bytes = 848 kB Load Address: 11000000 Entry Point: 11000000 Loading Kernel Image ... OK OK Starting kernel ... uimage's file name is "bootstrap_hello.uimage". "bootstrap_hello.uimage" has information such as "bootstrap_hello.uimage: u-boot legacy uImage, L4 Image #2, Linux/ARM, OS Kernel Image (Not compressed), 868352 bytes, Thu Mar 20 13:14:42 2014, Load Address: 0x11000000, Entry Point: 0x11000000, Header CRC: 0xBEA251F3, Data CRC: 0xA0217B7D" I have a question. Can you tell me function name that means 'Entry Point: 0x11000000' ?

3 5

Fwd: Can you tell me function name that means 'Entry Point: 0x11000000' ?
by TaeWoong Song 23 Mar '14

23 Mar '14

Begin forwarded message: > From: Taeung <treeze.taeung(a)gmail.com> > Subject: Re: Can you tell me function name that means 'Entry Point: 0x11000000' ? > Date: March 23, 2014 12:07:38 PM GMT+09:00 > To: Matthias Lange <matthias.lange(a)kernkonzept.com> > > Thank you , Matthias :-) > > Fortunately , Ahmed in L4 hackers give me a patch about UART on Freescale imx6q sabre_sd. > > But i question , again. > > I have known that entry point mean the address of the execution of the image. > But i really want to know that.. > > What is concreate function name mapping the address in L4 re source code ? > > - Taeung - > > On 03/22/2014 07:02 AM, Matthias Lange wrote: >> Hi, >> >>> On 21 Mar 2014, at 11:33, Taeung <treeze.taeung(a)gmail.com> wrote: >>> >>> Hello, l4 hacker. >>> >>> >>> I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE SD board(Cortex-A9, ARMv7). >>> >>> I'm using 'u-boot' and 'uImage'. >>> So, i build uimage by "make uimage E=hello ~...". >>> And i've try to booting it on Freescale i.MX6q_sabre_sd board. >>> But i did not it because stoped at "Starting kernel ..." !! >> Probably you selected the wrong UART, so the system is not printing something on the serial line. Make sure you have the right UART driver for your platform and make sure you have selected the right one. Usually there are more than one UARTs and only one is connected to you serial line. You can also check Linux to see which UART it uses. >> >>> MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK >>> ## Booting kernel from Legacy Image at 10800000 ... >>> Image Name: L4 Image #2 >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 868352 Bytes = 848 kB >>> Load Address: 11000000 >>> Entry Point: 11000000 >>> Loading Kernel Image ... OK >>> OK >>> >>> Starting kernel ... >>> >>> >>> uimage's file name is "bootstrap_hello.uimage". >>> "bootstrap_hello.uimage" has information such as >>> "bootstrap_hello.uimage: u-boot legacy uImage, L4 Image #2, Linux/ARM, OS Kernel Image (Not compressed), 868352 bytes, >>> Thu Mar 20 13:14:42 2014, Load Address: 0x11000000, Entry Point: 0x11000000, Header CRC: 0xBEA251F3, Data CRC: 0xA0217B7D" >>> >>> I have a question. >>> >>> Can you tell me function name that means 'Entry Point: 0x11000000' ? >> In the uimage format the entry point is defined as the address where uboot should start, as the name implies, the execution of the image. >> >> >> Matthias. >

2 1

compile l4re for arm
by Waldo 21 Mar '14

21 Mar '14

Hi, i am running the hello world example for the arm realview (exynos4412), and i don't how create a elfimage to run the example, i compile the fiasco and l4re for arm, but the elfimage is not generated.

3 3

Google Summer of Code - DEADLINE IS TODAY!
by Crypto Stick 21 Mar '14

21 Mar '14

Hi! Crypto Stick is an open source secure USB device for data encryption and authentication. OpenCoin is an open source system for anonymous cash. We (both projects) are aiming to collaborate on building a L4-based server system which would act as an eCash issuer server. Now, we got accepted at the upcoming Google Summer of Code 2014, which means that Google will sponsor a student working on this project during the summer with $5500. If this sounds interesting for you, please get in touch with us! Also, please share the word with fellow students. THE APPLICATION DEADLINE IS TODAY 19:00 UTC! Sorry for this last minute announcement. More details are available at: https://www.assembla.com/spaces/cryptostick/wiki/Ideas Best regards, Jan

1 0

L4 Fiasco's scheduling in Multi-Core
by Ganis Zulfa Santoso 20 Mar '14

20 Mar '14

Hi l4-hackers, Suppose we have 2 cores (core 0 and core 1) and we have 2 tasks (task A and task B). And I assign all threads of task A to run in core 0 and all threads of task B to run in core 1. How L4 Fiasco's scheduler manages this? Will the tasks run together or they have to switch from one to another? >From what I understand, the tasks don't run together regardless which core they are located, is it correct? Thank you. Best regards, Ganis

3 2

compiling L4RE for ARM
by Waldo 18 Mar '14

18 Mar '14

hello, i am a beginner in this topic, but you can tell me how i can compile L4re for ARM ?

2 1

I was not able to run "Hello world" on my board(imx6).
by taeung 18 Mar '14

18 Mar '14

Hello, L4 hackers. I have questions about booting "Hello world" on myboard. Please help me. I'm try to boot "Hello world + L4re + fiasco" on my board of which name is 'freescale i.MX6 Quad SABRE SD'(Cortex-A9,ARMv7). I built L4re and Fiasco. So, i got L4 build tree and fiasco image. Although i have built uimage file by "make uimage" and and i try to "make qemu", i was not able to run "hello world". (For reference,i have run original linux of which name is Linux/ARM, OS Kernel ,Linux-3.0.35-2508-g54750ff on my board(Freescale imx6q_sabre_sd)) <1. Result of the try booting on my board after "make uimage"> ======================================================================== MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #3 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1224704 Bytes = 1.2 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... ======================================================================== <1-1. My Question > Why stop at "Starting kernel..." ? Is wrong my environment variables in u-boot ? (If it is the problem, how fix u-boot environment variables from '1-4'? ) Or, my toolchains(linaro gcc 4.6 (64bit) ) are a wrong choice ? <1-2. Fiasco : What i configured for myboard > ======================================================================== Target configuration ---> Architecture (ARM processor family) Platform (Freescale i.MX) Freescale i.MX (i.MX6) CPU (ARM Cortex-A9 CPU) [ ] Enable alignment check (NEW) [ ]Execution Model (Standard mode) [ ] Enable the deprecated 'swp' instruction (NEW) [*] Enable L2 Cache [ ] Enable FPU co-processor [ ] Enable CPU errata workarounds (NEW) Kernel options ---> [*] Enable multi processor support (4) Maximal supported number of CPUs (NEW) [*] Fine-grained CPU time Scheduler (Fixed priority scheduler) ======================================================================== <1-3. L4 re : What i configured for myboard> ======================================================================== Target Architecture 3. ARM architecture (BUILD_ARCH_arm) (NEW) CPU variant 9. ARMv7A type CPU (CPU_ARM_ARMV7A) (NEW) Platform Selection 7. Freescale i.MX6 (PLATFORM_TYPE_imx6) (NEW) Automatically determine internal gcc preprocessor names (INT_CPP_NAME_SWITCH) [Y/n] (NEW) Y Automatically determine internal ld names (INT_LD_NAME_SWITCH) [Y/n] (NEW) Y Strip binaries on install (BID_STRIP_PROGS) [N/y/?] (NEW) N GCC: Omit Frame-pointers (BID_GCC_OMIT_FP) [N/y/?] (NEW) N Build doc directories (BID_BUILD_DOC) [N/y/?] (NEW) N Enable RELEASE flag (RELEASE_MODE) [N/y/?] (NEW) N ======================================================================== <1-4. U-boot : what i set environment variable for my board> (u-boot-mx6q-sabresd.bin is supported from freescale home page.) ======================================================================== MX6Q SABRESD U-Boot > setenv loadaddr 0x10800000 MX6Q SABRESD U-Boot > setenv bootargs_base 'setenv bootargs console=ttymxc0,115200' MX6Q SABRESD U-Boot > setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk1p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24' MX6Q SABRESD U-Boot > setenv bootcmd_mmc 'run bootargs_base bootargs_mmc;mmc dev 2;mmc read ${loadaddr} 0x800 0x2000;bootm' MX6Q SABRESD U-Boot > setenv bootcmd 'run bootcmd_mmc' MX6Q SABRESD U-Boot > saveenv Saving Environment to MMC... Writing to MMC(2)... done MX6Q SABRESD U-Boot > run bootcmd ======================================================================== <2. Result of the second try "make qemu"> ======================================================================== root@taeung-MS-7798:/path/to/obj2/tudos# make qemu E=hello-cfg MODULE_SEARCH_PATH=/path/to/obj2/fiasco/ make[1]: Entering directory `/home/taeung/Hello_test_l4/src/l4' ... Generating bootstrap.ld Building entry "hello-cfg". Merging image /path/to/obj2/fiasco//fiasco to mod00 [360kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/sigma0 to mod01 [351kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/moe to mod02 [2365kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/l4re to mod03 [1228kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/ned to mod04 [2387kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/hello.cfg to mod05 [1kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/hello to mod06 [896kB] ... Compiling exec.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling region.o ... Compiling startup.o ... Compiling init_kip_v2.o ... Compiling init_kip_v4.o ... Compiling libc_support+.o ... Compiling patch.o ... Compiling koptions.o ... Compiling platform/imx.o ... Compiling loader_mbi.o ... Compiling ARCH-arm/reboot.o ==> Linking bootstrap.elf ==> Post-processing bootstrap.elf ==> "bootstrap.elf" built ==> Installing bootstrap.elf in image directory ==> Installing bootstrap_hello-cfg in image directory ==> Installing bootstrap_hello-cfg.elf in image directory Image size(s) in bytes: bootstrap_hello-cfg.elf: 1257856 Start address: 0x11000000 --> Build-Nr: 4 ==> Installing bootstrap.elf to local build-tree ==> Installing bootstrap_hello-cfg to local build-tree ==> Installing bootstrap_hello-cfg.elf to local build-tree QEmu-cmd: qemu-system-arm -kernel /path/to/obj2/tudos/images/bootstrap.elf qemu: fatal: Trying to execute code outside RAM or ROM at 0x11000000 R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=11000000 PSR=400001d3 -Z-- A svc32 s00=00000000 s01=00000000 d00=0000000000000000 s02=00000000 s03=00000000 d01=0000000000000000 s04=00000000 s05=00000000 d02=0000000000000000 s06=00000000 s07=00000000 d03=0000000000000000 s08=00000000 s09=00000000 d04=0000000000000000 s10=00000000 s11=00000000 d05=0000000000000000 s12=00000000 s13=00000000 d06=0000000000000000 s14=00000000 s15=00000000 d07=0000000000000000 s16=00000000 s17=00000000 d08=0000000000000000 s18=00000000 s19=00000000 d09=0000000000000000 s20=00000000 s21=00000000 d10=0000000000000000 s22=00000000 s23=00000000 d11=0000000000000000 s24=00000000 s25=00000000 d12=0000000000000000 s26=00000000 s27=00000000 d13=0000000000000000 s28=00000000 s29=00000000 d14=0000000000000000 s30=00000000 s31=00000000 d15=0000000000000000 FPSCR: 00000000 bash: line 3: 5158 Aborted (core dumped) $qemu -kernel /path/to/obj2/tudos/images/bootstrap.elf make[1]: *** [qemu] Error 134 make[1]: Leaving directory `/home/taeung/Hello_test_l4/src/l4' make: *** [qemu] Error 2 ======================================================================== <2-1. My Question > Qemu support cpu such as cortex-A9 and ARMv7. But it not support mahine information for Freescale i.MX6 quad sabre sd. Because this is the reason, Can't boot "Helloworld + L4re+Fiasco" by qemu ? Or Is there other reason ? Thank you, if you help whatever. /Regards, Taeung Song | Student of Computer Engineering Hansung University./

1 0

In Freescale i.MX6q_sabre_sd,The problem booting Helloworld + L4 + Fiasco
by taeung 17 Mar '14

17 Mar '14

Hello, L4 hackers. I have one question. please help me.. I have failed booting 'L4 Linux + L4 + Fiasco' on my board(Freescale i.MX6 Quad SABRE SD : Cortex-A9 , ARMv7) So, i'm try to boot 'Helloword + L4 + Fiasco' on my board Such as.. |$ svn cathttp://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - inithttp://svn.tudos.org/repos/oc/tudos fiasco l4re | 1. L4 Re : configure and build (Success) |||==========================================================================| $ mkdir -p /path/to/obj/tudos |$ make O=/path/to/obj/tudos oldconfig $ make O=/path/to/obj/tudos -j2| |========================================================================== | |2. Fiasco : configure and build (Success)| || |========================================================================== $ cd /somedir/tudos/src/kernel/fiasco $ make BUILDDIR=/path/to/obj/fiasco $ cd /path/to/obj/fiasco $ make menuconfig $ make ========================================================================== 3. But,when i try to 'make uimage' or 'make qemu', error is happened. such as.. ========================================================================== root@taeung-MS-7798:/path/to/obj2/tudos# make uimage E=hello-cfg MODULE_SEARCH_PATH=/path/to/obj2/fiasco/ make[1]: Entering directory `/home/taeung/Hello_test_l4/src/l4' =========== Updating RAM_BASE for platform imx6 to 0x10000000 ========= ... Regenerating RAM_BASE settings Library dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys in directory '/home/taeung/Hello_test_l4/src/l4/pkg/sigma0/server/src'; aborting. /home/taeung/Hello_test_l4/src/l4/mk/binary.inc:348: *** Cflags dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys in directory '/home/taeung/Hello_test_l4/src/l4/pkg/sigma0/server/src'; aborting.. Stop. make[2]: *** [/path/to/obj2/tudos/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f] Error 2 make[1]: *** [check_and_adjust_ram_base] Error 2 ========================================================================== |<< My Question >> Although i search of '|Library dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys|' in google.com, i could'nt get information about this error. I don't know why the problem is happened updating |'RAM_BASE for platform imx6 to 0x10000000'. | || Please any help.. /Regards, Taeung Song | Student of Computer Engineering Hansung University./

2 2

L4Linux + L4re + Fiasco to boot in Freescale i.MX6q_sabre_sd
by taeung 17 Mar '14

17 Mar '14

Hello L4 hackers. I have two question (My question 1, 2 ). please help me. I'm trying to boot 'L4Linux + L4re + Fiasco' in Freescale i.MX6 Quad SABRE SD board (Cortex-A8, ARMv7-A). Such as.. 0. Get Source and install required package. |$ cd /somedir/tudos $ svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos fiasco l4re l4linux_requirements| 1. L4 Re : configure and build (Success) |||==========================================================================| $ mkdir -p /path/to/obj/tudos |$ make O=/path/to/obj/tudos oldconfig $ make O=/path/to/obj/tudos -j2| |==========================================================================| 2. Fiasco : configure and build (Success) |==========================================================================| ||$ cd /somedir/tudos/src/kernel/fiasco |$ make BUILDDIR=/path/to/obj/fiasco $ cd /path/to/obj/fiasco $ make menuconfig $ make| |==========================================================================| 3. L4 linux : configure and build. (Failure) (Here, i have trouble to build l4 linux after configure according to my board ) |==========================================================================| |$ cd /somedir/tudos $ svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux $ cd l4linux $ mkdir /path/to/obj/l4linux $ make L4ARCH=arm CROSS_COMPILE=arm-linux- O=/path/to/obj/l4linux arm_defconfig # In the menu, in "L4Linux configuration", set "L4 tree build directory" to /path/to/obj/tudos $ make L4ARCH=arm CROSS_COMPILE=arm-linux- O=/path/to/obj/l4linux menuconfig ||==========================================================================| To configure according to my board(Freescale i.MX6q_sabre_sd), I was able to choice two kinds. <The first > |System type -> ARM system type (L4 Linux) Build type (Use ARMv7) | <Result of the first > 1) Sucess build L4 linux and i got 'vmlinuz.arm' 2) 'make uImage' according to module.list |========================================================================== entry L4Linux_xs_2 kernel fiasco -nokdb roottask moe rom/l4linux.cfg module l4linux.cfg module l4re module ned module vmlinuz.arm module ramdisk-arm.rd| |==========================================================================| 3) i make SD Card bootable by u-boot.bin and bootstrap.uImage 4) Booting L4Linux + L4re + Fiasco in Freescale i.MX6q_sabre_sd But, i have problem to boot it. =========================================================================== U-Boot 2009.08 (Aug 16 2013 - 12:04:20) CPU: Freescale i.MX6 family TO1.2 at 792 MHz Thermal sensor with ratio = 180 Temperature: 44 C, calibration data 0x5764ba7d mx6q pll1: 792MHz mx6q pll2: 528MHz mx6q pll3: 480MHz mx6q pll8: 50MHz ipg clock : 66000000Hz ipg per clock : 66000000Hz uart clock : 80000000Hz cspi clock : 60000000Hz ahb clock : 132000000Hz axi clock : 264000000Hz emi_slow clock: 132000000Hz ddr clock : 528000000Hz usdhc1 clock : 198000000Hz usdhc2 clock : 198000000Hz usdhc3 clock : 198000000Hz usdhc4 clock : 198000000Hz nfc clock : 24000000Hz Board: i.MX6Q-SABRESD: unknown-board Board: 0x63012 [POR ] Boot Device: SD I2C: ready DRAM: 1 GB MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3 In: serial Out: serial Err: serial i2c: I2C3 SDA is low, start i2c recovery... I2C3 Recovery success Found PFUZE100! deviceid=10,revid=11 Net: got MAC address from IIM: 00:04:9f:02:70:b5 FEC0 [PRIME] Hit any key to stop autoboot: 0 mmc2 is current device MMC read: dev # 2, block # 2048, count 17408 ... 17408 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 7680000 Bytes = 7.3 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... ========================================= <My question 1.> Why hang at 'Starting kernel ...' ? Setting environment variable and bootcmd , i have thought the setting is no problem. This kernel image is wrong? <The Second > |System type ---> ARM system type (Allow multiple platforms to be selected)| Multiple platform selection ---> ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait) Build type Freescale i.MX family Freescale i.MX support ---> i.MX6 Quad/DualLite support <Result of the second > i could not build l4 linux because.. GEN /path/to/obj/l4linux/Makefile scripts/kconfig/conf --silentoldconfig Kconfig ERROR: CONFIG_ARM_PATCH_PHYS_VIRT must not be enabled. make[1]: *** [check_linux_config] Error 1 make: *** [sub-make] Error 2 <My question 2.> Why can not build L4 linux according to this config ? and What is CONFIG_ARM_PATCH_PHYS_VIRT ? Please any help.. /Regards, Taeung Song | Student of Computer Engineering Hansung University. /

2 1

Re: Problem in Linking program
by Irvanda Kurniadi 13 Mar '14

13 Mar '14

Case closed. I found that the __assert_fail is not supported in uclibc. Then, I tried to change __assert_fail with __assert and it works. But I'm still curious about using glibc in L4re. I try to compile my program using libgcc but it also doesn't work. Can it cause any problem if I use glibc compiler than any of requires_libs using uclibc compiler? just wondering irvanda

2 1

Problem in Linking program
by Irvanda Kurniadi 12 Mar '14

12 Mar '14

Hi, I'm trying to build my program in L4/Fiasco. This program requires libtiff, MPI, and libstep library. I've ported those all libraries. But, when I built my program, I got a problem in linking program. The compilation just work fine but when entering the linking part, I got this error message: ==> Linking sobel-step ........ main-sobel-V4.cpp_processed.o: In function `main': /home/l4re-mpich/src/l4/pkg/sobel-step/server/src/main-sobel-V4.cpp_processed.c:57: undefined reference to `__assert_fail' /home/l4re-mpich/src/l4/pkg/sobel-step/server/src/main-sobel-V4.cpp_processed.c:56: undefined reference to `__assert_fail' ......... This "__assert_fail" should be available in libstep.so and I've put the LDFLAGS = -lstep on my makefile. Here is my Makefiel anyway: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. SYSTEMS = x86-l4f amd64-l4f include $(L4DIR)/mk/Makeconf ifneq ($(SYSTEM),) # check whether used gcc has the omp.h file available OMP_H_PATH := $(shell $(CC) -print-file-name=include/omp.h) ifeq ($(strip $(OMP_H_PATH)),include/omp.h) $(info [32m $(CC) does not have omp.h header file available, skipping.[0m) else TARGET = $(if $(filter 4.2 4.3 4.4 4.5 4.6 4.7,$(GCCVERSION)),sobel-step) REQUIRES_LIBS = libgomp libtiff libmpich libmpich_f77sup libstep libc libc_support_misc endif endif SRC_C = main-sobel-V4.cpp_processed.c sobel-omp-V4.cpp_processed.c pictureInterface.c util.c CFLAGS += -fopenmp -I. -g -Wall LDFLAGS += -rpath -ltiff -rpath -lstep PRIVATE_INCDIR = $(SRC_DIR) vpath %.c $(SRC_DIR) include $(L4DIR)/mk/prog.mk Previously I compiled the program and there are so much missing shared libraries and the debug message suggested to add the -rpath. I updated my LDFLAGS by adding the -rpath. Here is the error message before I add the LDFLAGS with -rpath: ==> Linking sobel-step .... ld: warning: libl4z.so, needed by /home/l4re-mpich/obj/l4/x86/lib/x86_586/l4f/libtiff.so, not found (try using -rpath or -rpath-link) ld: warning: libgfortran.so, needed by /home/l4re-mpich/obj/l4/x86/lib/x86_586/l4f/libstep.so, not found (try using -rpath or -rpath-link) ....... ld: final link failed: Bad value I'm not sure whether this is causing another problem by adding the -rpath. I mean, Is it the proper way to fix the missing shared library? Because the "__asser_fail" is supposed to be found in the libstep.so but I still got the undefined reference error message. So perhaps there are several things to wrap up this linking problem. If you by any chance find any misplace or missing configuration in my makefile or you have any idea how to fix it please let me know. Thanks Regards, Irvanda

1 0

seL4 what exactly is in the kernel
by Taylor Bioniks 11 Mar '14

11 Mar '14

Like all L4 kernels, it provides basic mechanisms which must be in the kernel for security reasons. These include low-level interrupt and exception handlers (which essentially convert these events into IPC messages to user-level handlers), a notion of address spaces into which you can map frames (basically an abstraction of page tables), a notion of kernel-scheduled (and context-switched) threads, a notion of a protection domain (capability tree) and a communication and synchronisation mechanism (IPC endpoints). Other L4 kernels have similar abstractions. Please explain what you mean by notion? Do you mean that it has code to deal with the user mode memory management and such? What is different in seL4 is that all memory management is done at user level. After booting up and allocating and initialising its static data structures (scheduling queues, the kernel stack and a few globals) the kernel sets up an initial user address space with a single thread, and hands it the rights to all remaining memory (in the form of "Untyped" capabilities). When performing an operation that requires kernel data structures (eg creating a thread requires creating a thread control block, TCB) the user has to provide these, by "retyping" some Untyped memory into a kernel object type. This makes it kernel memory (inaccessible to userland), but the owner of that memory can always revoke it (revert it to Untuped, thus nuking the kernel object). so is the single kernel stack in it's own address space or is it somehow mapped or shared with other address spaces? There's a single kernel stack, which is in use whenever kernel code executes. The terms "kernel mode" or "user mode" make no sense for data - they refer to the processor mode that is active when particular code is executing. However, the kernel stack is, of course, a kernel object, only accessible in kernel mode. While the kernel stack (like the scheduler queues) is somewhat special, in that it is allocated by the kernel at boot time, in terms of accessibility it's no different from other "kernel objects", such as PTs or TCBs, that are allocated by userland. so kernel objects are stored in this user mode kernel stack? Okay, so the kernel never actually has a stack in kernel mode, and it never allocates space for itself does this mean that the kernel does not grow? And if so does that eliminate the requirement that I've seen on X86 machines where they have 1GB for the kernel and 3GB for the user programs Final thing is I've been pointed to the university site a few times and I've been told there are slides with audio on there, however, I can never find them even after mirroring the site and looking through it. Where might I find these?

2 1

Problem when booting L4 Fiasco/Re
by Sören Jonsson 11 Mar '14

11 Mar '14

Hello, I have now successfully compiled the L4 Fiasco.OC and your runtime environment. I made the hello.iso bootable image as well, and made an attempt to run it under VMWare workstation. My problem is that it don't work. It stops during boot, with the following information: I had to provide two images, in order to capture all information. The information above "Total RAM: 255MB" disapers very fast otherwise. Is this enough information to explain what is happening, or can I provide more information using other methods? With my best regards, Sören Jonsson Sweden

2 1

seL4 what exactly is in the kernel
by Taylor Bioniks 08 Mar '14

08 Mar '14

What does the seL4 kernel actually provide in the kernel itself? I've read through documentation and it seems they just stop before they state exactly what the seL4 kernel does. So what I'd like to know is what features and components are in the kernel and what is outside of it? Does the kernel have a single kernel stack or multiple kernel stacks and is/are it/they in kernel mode or user mode? Are there any good diagrams that show how seL4 works with its user space components? Thanks in advance

2 1

Panic with l4Linux
by Ismael BARAKAT 07 Mar '14

07 Mar '14

Hello, I'm working on Fiasco, l4Re and l4Linux. I build the uImage for an arm architecture. When I boot it, I have a "panic: going to sleep forever, bye". Can someone help I don't know what caused the problem. This is the information I have on my console when I boot: L4 Bootstrapper Build: #10 Thu Mar 6 11:11:19 CET 2014, 4.7.3 Scanning up to 128 MB RAM Memory size is 128MB (80000000 - 87ffffff) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB mod07: 813f7000-816f7000: ramdisk-arm.rd mod06: 81125000-813f6480: vmlinuz.arm mod05: 81124000-81124189: l4Linux.cfg mod04: 810d1000-81123bc0: ned mod03: 810b7000-810d0458: l4re mod02: 81085000-810b6624: moe mod01: 8107b000-8108433c: sigma0 mod00: 81015000-8107a3a8: fiasco Moving up to 8 modules behind 81100000 moving module 00 { 81015000-8107a3a7 } -> { 817e2000-818473a7 } [414632] moving module 01 { 8107b000-8108433b } -> { 81848000-8185133b } [37692] moving module 02 { 81085000-810b6623 } -> { 81852000-81883623 } [202276] moving module 03 { 810b7000-810d0457 } -> { 816f7000-81710457 } [103512] moving module 04 { 810d1000-81123bbf } -> { 81711000-81763bbf } [338880] moving module 05 { 81124000-81124188 } -> { 81100000-81100188 } [393] moving module 06 { 81125000-813f647f } -> { 81101000-813d247f } [2954368] moving module 07 { 813f7000-816f6fff } -> { 813d3000-816d2fff } [3145728] moving module 03 { 816f7000-81710457 } -> { 816d3000-816ec457 } [103512] moving module 04 { 81711000-81763bbf } -> { 816ed000-8173fbbf } [338880] Scanning fiasco Scanning sigma0 Scanning moe rom/l4Linux.cfg Relocated mbi to [0x8100e000-0x8100e12a] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80001000, 80001b3f] { b40} Kern fiasco [ 80002000, 80072fff] { 71000} Kern fiasco [ 80090000, 800965fb] { 65fc} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8016cacb] { 2cacc} Root moe [ 80170000, 80186f0f] { 16f10} Root moe [ 81000000, 810143f3] { 143f4} Boot bootstrap [ 8100e000, 8100e227] { 228} Root Multiboot info [ 81100000, 8173fbbf] { 63fbc0} Root Module API Version: (87) experimental Sigma0 config ip:80090100 sp:81013de4 Roottask config ip:80140260 sp:00000000 Starting kernel fiasco at 80001300 Hello from Startup::stage2 Cache config: ON ID_PFR[01]: 00001131 00000011 ID_[DA]FR0: 00010400 00000000 ID_MMFR[04]: 01100003 20000000 01202000 00000211 Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned director compiled with gcc 4.7.3 for Beagleboard [] Build: #1 Wed Mar 5 17:15:13 CET 2014 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:80000000;80000fff] [0:80073000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;8016cfff] [0:8016d000;8016ffff] [4:80170000;80186fff] [0:80187000;8100dfff] [4:8100e000;8100efff] [0:8100f000;810fffff] [4:81100000;8173ffff] [0:81740000;86ffffff] IOMEM:---------------------- [0:0;7fffffff] [0:88000000;ffffffff] MOE: Hello world MOE: found 107500 KByte free memory MOE: found RAM from 80000000 to 87000000 MOE: allocated 112 KByte for the page array @0x80073000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [816d3000-816ec458] [C:503000] l4re BOOTFS: [816ed000-8173fbc0] [C:504000] ned BOOTFS: [81100000-81100189] [C:505000] l4Linux.cfg BOOTFS: [81101000-813d2480] [C:506000] vmlinuz.arm BOOTFS: [813d3000-816d3000] [C:507000] ramdisk-arm.rd MOE: cmdline: moe rom/l4Linux.cfg MOE: Starting: rom/ned rom/l4Linux.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4Linux.cfg' l4Linux | libio: Warning: Query of 'vbus' failed! l4Linux | PH 0 (t: 1) offs=00008000 vaddr=01000000 vend=01331b1c l4Linux | phys=01000000 ephys=01331b1c l4Linux | f_sz=002b33d4 memsz=00331b1c flgs=rwx l4Linux | PH 1 (t: 4) offs=002bb3b0 vaddr=012b33b0 vend=012b33d4 l4Linux | phys=012b33b0 ephys=012b33d4 l4Linux | f_sz=00000024 memsz=00000024 flgs=r-x l4Linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4Linux | phys=00000000 ephys=00000000 l4Linux | f_sz=00000000 memsz=00000000 flgs=rwx l4Linux | Starting binary at 0x10002a0, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4Linux | External resolver is at 0xa8000794 l4Linux | ======> L4Linux starting... <======== l4Linux | Linux version 3.7.0-l4-svn30 (juliens@ubuntu) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #1 Wed May 29 10:25:09 CEST 2013 l4Linux | Binary name: rom/vmlinuz.arm l4Linux | This is an AEABI build. l4Linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh l4Linux | CPU mapping (l:p)[1]: 0:0 l4Linux | Image: 01000000 - 01400000 [4096 KiB]. l4Linux | Areas: Text: 01000000 - 01290000 [2624kB] (a bit longer) l4Linux | Data: 01290000 - 012aeee0 [123kB] l4Linux | Initdata: 01273000 - 0128ed7c [111kB] l4Linux | BSS: 012b33d4 - 01331b1c [505kB] l4Linux | Device scan: l4Linux | Device scan done. l4Linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:01291fa4) l4Linux | main thread will be 413 l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | section-with-init: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | section-with-init: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | Main thread running, waiting... l4Linux | L4x: Setting superpages for main memory l4Linux | Main memory size: 64MB l4Linux | Main memory: virt: 0x1400000 to 0x53fffff [65536 KiB] l4Linux | Main memory: Phys: 0x81800000 to 0x85800000, Size: 67108864 l4Linux | Filling lower ptabs... l4Linux | Done (220 entries). l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | text: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | text: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | l4x_rd_path: rom/ramdisk-arm.rd l4Linux | Loading: rom/ramdisk-arm.rd l4Linux | INITRD: Size of RAMdisk is 3072KiB l4Linux | RAMdisk from 0d400000 to 0d700000 [3072KiB] l4Linux | panic: going to sleep forever, bye Kinds regards and thanks for the help, Ismaël Barakat

2 1

Seting Library search path
by Sören Jonsson 06 Mar '14

06 Mar '14

Hello, I am interested in L4 Fiasco as a virtualization environment. I am currently attempting to compile the L4 runtime environment, and I am getting the following error message: === Building package "bootstrap" === ==> Linking bootstrap32.elf /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: error: ld returned 1 exit status make[5]: *** [bootstrap32.elf] Error 1 make[4]: *** [/home/osj/l4re/build/pkg/bootstrap/server/src/OBJ-amd64_amdfam10] Error 2 make[3]: *** [src] Error 2 make[2]: *** [server] Error 2 make[1]: *** bootstrap] Error 2 make: *** [pkg] Error 2 I have examined the problem, and can see that I have a library /usr/lib/gcc/x86_64-linux-gnu/4.7.2, as well as the /usr/lib/gcc/x86_64-linux-gnu/4.7. Can the problem be that the linker is attempting to link to a dated version of the library, and what is the best way to resolve this problem? Best regards, Sören Jonsson Sweden

2 1

Running application can't create a file
by Irvanda Kurniadi 03 Mar '14

03 Mar '14

Hi, Recently I'm using libtiff library on L4/Fiasco. I can use some function from that library. But when I'm trying to create an image by using libtiff function, I got this error message: TIFFOpen: output.tif: Cannot open. Could not open output.tif for writing MOE: task 1561539 exited with 42 Here is my configuration in module.list entry tiff_test2 roottask moe --init=rom/tiff_test2 module l4re module tiff_test2 I compile and run it over linux and it works properly. This application is supposed to create the output file and then open it by TIFFOpen function. So, I think there is a trick to launch this tiff application over L4/fiasco, so the kernel can permit the application to create a file. But, it's only my assumption and I'm not really sure about this. If by any chance you know something about it, please let me know. Thanks regards, Irvanda

2 3

Framebuffer in L4Re for Raspberry PI
by Peter Hanzel 03 Mar '14

03 Mar '14

Hello. I have compiled Fiasco.OC and L4Re for Raspberry PI. It boots ok with UART output. Now I want to add framebuffer device and output to monitor. Is this a work in progress or is it already implemented? or to be implemented? Thanks.

4 4

Genode 14.02 enables VirtualBox on NOVA
by Christian Helmuth 28 Feb '14

28 Feb '14

Today we released a new version of Genode, which, beside many other improvements, adds support for VirtualBox as VMM on NOVA. For years, we addressed virtualization in Genode beginning with OKLinux on the OKL4 kernel. Later, we added support for L4Linux on Fiasco.OC and the Vancouver/Seoul VMM on NOVA. All these solutions had strong points in distinct usage scenarios but we always missed support for a wide range of guest OSes, guest-host integration features, ease of use, active development, and, finally, support for MS Windows guests. Therefore, we are happy to have enabled VirtualBox on the NOVA microhypervisor now, which brings all these features and (due to NOVA's virtualization support) integrates perfectly with the architecture of Genode. Besides VirtualBox, the main features and improvements of the current release are: - Base framework - Improved stack management - Storage - NetBSD file systems ported via rump kernels - Revised block-driver framework - New block cache - New FUSE-based NTFS-3g support - Ported e2fsprogs to the Noux runtime - Low-level OS infrastructure - New pseudo file system as tracing front end - Unified interfaces for graphics - New status-reporting mechanism - Nitpicker support for dynamic screen resizing - Libraries and applications - Extended Noux runtime with POSIX signals - Dynamic ROM service - Platforms - Basic support ODROID XU More details about version 14.02 can be found in the release documentation here http://genode.org/documentation/release-notes/14.02 Best regards -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

L4 Performance
by Gernot Heiser 24 Feb '14

24 Feb '14

Given the recent discussions re IPC performance, I thought it’d be helpful to summarise the state of the art. I’ve put up a performance page on http://l4hq.org (linked from the home page) showing IPC latencies of various L4 kernels across 20 years of architectures. It’s an expanded version of what’s in [Elphinstone & Heiser, SOSP’13]. Each entry in there is, AFAIK, the fastest ever-reported IPC performance of any full-semantics microkernel (i.e. not jsut L4, it’s just that no non-L4 kernel ever broke any records in the last 20 years). If you have any data to contribute please let me know. Gernot

1 0

Fortran Compiler Missing
by Irvanda Kurniadi 22 Feb '14

22 Feb '14

Hi, I have some problem in building some package. It is a little bit weird because the packages just compiled fine in my office, but when I tried to build the same package on the same system in my laptop using VMware, I got this debug message: Fortran compiler (gcc-4.6 or later) missing, skipping directory '/home/..' Since the other package requires the library which is supposed to be built by fortran compiler, then I got this error message: Library dependencies missing: libmpich_f77sup in directory '/home/..'; aborting. I don't know why this problem occur when it worked just fine in another PC. regards, Irvanda

2 2

Library dependencies missing: stdlibs in directory
by Emanuel Berg 21 Feb '14

21 Feb '14

I tried to do exactly as your 'hello' application to see if I could compile and link. Among some other output, I got this message on 'make O=obj_path': Library dependencies missing: stdlibs in directory '/home/incal/core/l4re-snapshot-2013123021/src/l4/pkg/hi/server/src'; aborting. Cflags dependencies missing: stdlibs in directory '/home/incal/core/l4re-snapshot-2013123021/src/l4/pkg/hi/server/src'; aborting. Stop. Before I did that, it told me to 'make O=obj_path config' from src/l4, which I did, though I didn't setup anything explicitly. I had to fetch 'pkg-config' from the repos, but that worked great, only it wouldn't work less the terminal had at least 80 columns - turns out, in the Linux VT, I have 73 columns (i.e., char width), and in X, in urxvt 78. But xterm was configurable in .Xresources like this: xterm*geometry: 80x28 Just sayin'. What is "stdlibs"? It sounds like the C standard library except for the trailing "s". I tried to remove the "include" stuff from the C source, as well as the 'puts' and 'sleep' (to just make it return 0) - this, I thought, would make it independent of any library routines, however, I got the same error message. -- underground experts united: http://user.it.uu.se/~embe8573

4 16

Build kernel modules and run it on L4linux
by Irvanda Kurniadi 19 Feb '14

19 Feb '14

Hi, Have you tried to build kernel modules and run it on L4linux? I read [1] and followed the instructions given by that document. 1. I built a "Hello world" Kernel module by following [2], then I got my .ko file. 2. I mounted my L4linux Ramdisk and copied my hello.ko into the Ramdisk 3. In src/l4/conf/examples/l4lxgfx.cfg, I add a kernel parameter: l4bdds.add=rom/hello.ko, as shown below: -- Start Linux loader:start( { .......... }, "rom/" .. lxname .. " mem=64M console=tty0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=/bin/sh l4bdds.add=rom/hello.ko"); But, when I booted the L4linux, I couldn't find the /dev/l4bdds0. Any opinion about this? Regards, Irvanda [1] http://os.inf.tu-dresden.de/Studium/KMB/WS2013/Exercise3-L4Linux.pdf [2] http://www.tldp.org/LDP/lkmpg/2.6/html/x181.html

2 6

Re: Re: Build kernel modules and run it on L4linux
by Irvanda Kurniadi 18 Feb '14

18 Feb '14

> > On 18.02.2014 07:36, Irvanda Kurniadi wrote: > > Hi, > > > > Have you tried to build kernel modules and run it on L4linux? I > > read [1] and followed the instructions given by that document. 1. I > > built a "Hello world" Kernel module by following [2], then I got > > my .ko file. > > Did you enable CONFIG_L4_BLK_DS_DRV in the L4Linux configuration? > Yes I did. I just checked the .config file # Stub drivers CONFIG_L4_BLK_DS_DRV=y regards, Irvanda

1 0

Hello!
by Blaine Garst 17 Feb '14

17 Feb '14

Greetings, all! I am beginning to explore nano/micro-kernel issues again after a long hiatus (24 years). I don’t know how active this list is nor its followers, so I will be brief. At the moment I am discussing kernel vs user scheduling speed bumps in the now prevalent multi-core cpu architectures in the context of the ISO C11 subcommittee CPLEX which is considering adding parallelization language extensions. I have already demonstrated feature equivalence using closures (Apple’s Blocks, which I introduced and have previously proposed for C11) and some new synchronization and scheduling primitives that I am already using as part of some Actor research. I am looking for a non-GPL kernel/executive/nano-kernel to redo some nano-kernel work I did as part of a joint Bell Labs-Sun collaboration that gave rise to SVR4 and, in opposition, the Open Software Foundation. Essentially I built a capability based nano-kernel somewhat along the lines of the V Kernel of David Cheriton (the Sun folks did “Spring”) My prototype at the time had IPC transfer speed of 10x vtable dispatch cost. At the time I wrote my own IDL, but after joining NeXT we added such a concept as a first class language feature, and it was copied into Java as “interfaces”. This is still an active interest of mine also in the context of Actors. Is this an appropriate list to discuss whether L4 is an appropriate starting point and such issues that might arise from my exploration? (My friends and former colleagues at Apple have IP restrictions such that I would prefer to not risk even the appearance of possible improprieties in discussing such matters) Blaine Garst

5 12

FOSDEM microkernel dinner
by Julian Stecklina 13 Feb '14

13 Feb '14

Hello fellow microkernel hackers, for those of you at FOSDEM: Some of us want to meet up for dinner tonight. I suggest we meet on Grand Place / Grote Markt at 20:30. This should leave everyone enough time to drop off their stuff at the hotel and get to the city center. Julian

2 1

building_l4re_pandaboard
by Комаров Тимофей 11 Feb '14

11 Feb '14

Hello, guys! I've successfully built the latest L4RE snapshot for beagleboard. Any apps and even L4Linux work like a charm. It simply rocks! Right now I'm trying to run the latest snapshot on pandaboard. I've successfully built it. Helloworld example is OK, but L4Linux gets a certain error while booting: l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=02362f1c l4linux | phys=02000000 ephys=02362f1c l4linux | f_sz=002de3b6 memsz=00362f1c flgs=rwx l4linux | PH 1 (t: 4) offs=002a16ec vaddr=022996ec vend=02299710 l4linux | phys=022996ec ephys=02299710 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002a0, argc=7 argv=0x80007f8c *argv=0xb1007ff0m l4linux | External resolver is at 0xa8000798 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.12.0-l4 (user1@debian) (gcc version 4.7.3 (Sourcery C4 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=romh l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 022b8000 [2784kB] (a bit longer) l4linux | Data: 022b8000 - 022d9200 [132kB] l4linux | Initdata: 0229a000 - 022b635c [112kB] l4linux | BSS: 022de3b6 - 02362f1c [530kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3551232 l4linux | section-with-init: Virt: 0x2000000 to 0x2362f1b [3467 KiB] l4linux | section-with-init: Phys: 0x8031e000 to 0x80680f1b, [3467 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x81900000 to 0x858fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3551232 l4linux | text: Virt: 0x2000000 to 0x2362f1b [3467 KiB] l4linux | text: Phys: 0x8031e000 to 0x80680f1b, [3467 KiB] l4linux | l4x_rd_path: rom/ramdisk-arm.rd l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | 'swp(b)' instruction at 021ec5a0 and faulting. l4linux | Linux built for the wrong ARM version? The last 2 lines are going to be repeated forever :-) I've tried both 4.7 and 4.8 gcc by Linaro and CodeSourcery and always get the same error. What can be a problem? Greetings! Looking forward for your help!

3 3

Passing Compilation Flag from CMake file
by Irvanda Kurniadi 11 Feb '14

11 Feb '14

Hi, I'm in the middle of porting OpenMPI. I got some trouble that I have to use CMakelists.txt to pass the Compilation Flag through Makefile. I got this error message while trying to compile: error: 'OMPI_MPIHANDLES_DLL_PREFIX' undeclared (first use in this function) error: 'OMPI_MSGQ_DLL_PREFIX' undeclared (first use in this function) And I found the OMPI_MPIHANDLES_DLL_PREFIX in CMakelist.txt as shown below: SET_TARGET_PROPERTIES(libmpi PROPERTIES COMPILE_FLAGS "${OMPI_C_DEF_PRE}OMPI_ MPIHANDLES_DLL_PREFIX=libompi_dbg_mpihandles ${OMPI_C_DEF_PRE}OMPI_MSGQ_DLL_PREFIX=libompi_dbg_msgq") Does anybody know how to use this CMake file? Regards, Irvanda

1 0

Re: Re: Re: Network Server Ankh
by Ajith Whowe 10 Feb '14

10 Feb '14

Dear Martin, These commands indicate that the link is always down with the "NO-CARRIER" flag. Please kindly refer to the outputs given below. This flag is set by the function "update_carrier", which checks 3 conditions, namely the i) priv->remote_attached ii) l4shmc_is_chunk_ready(&priv->tx_chunk) iii) l4shmc_is_chunk_ready(&priv->rx_chunk). Unfortunately the problem is originated at check point "l4shmc_is_chunk_ready". This function returns 0, the if clause fails and sets the link down. I just removed this check point from the if clause, set the link_up to 1 and observed that the ping request showed that the l4x_l4shmc_xmit_frame function is called. Nevertheless still no answer back from the second instance. What can be the main reason for the l4x_l4shmc_xmit_frame to return 0? Best Regards and many Thanks in Advance, The result for the "ip addr show" is as follows: XXXXX - XXXX: Inside l4x_l4shmc_get_stats function - start 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 52:54:00:b0:cf:02 brd ff:ff:ff:ff:ff:ff inet 192.168.124.116/24 scope global eth0 inet 192.168.0.5/24 scope global eth0:0 The result for the "ip link show" is as follows: XXXXX - XXXX: Inside l4x_l4shmc_get_stats function - start 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 52:54:00:b0:cf:02 brd ff:ff:ff:ff:ff:ff Hi Ajith, Am 07.02.2014 17:58, schrieb Ajith Whowe: >* Dear Martin, *>>* Thanks a lot. It did the job. I have the network interfaces on both *>* sides. Nevertheless I can not ping one another. The strange thing is the *>* ping request clearly does invoke any of the net_device_ops: *>>* static const struct net_device_ops l4shmnet_netdev_ops = { *>* .ndo_open = l4x_l4shmc_open, *>* .ndo_start_xmit = l4x_l4shmc_xmit_frame, *>* .ndo_stop = l4x_l4shmc_close, *>* .ndo_change_mtu = l4x_l4shmc_change_mtu, *>* .ndo_get_stats = l4x_l4shmc_get_stats, *>>* }; *>>* I put in all these functions some printk's and I can not see it once the *>* ping starts. *>>* I also did with -I option like: ping 192.168.1.2 -I eth0 but still no *>* success. *>* Do You have any idea? * If none of the functions are called, the packet get not through the IP stack. Can you post the IP configuration (ip addr show and ip link show) of of both partitions? Martin

2 1

Re: Re: Network Server Ankh
by Ajith Whowe 07 Feb '14

07 Feb '14

Dear Martin, Thanks a lot. It did the job. I have the network interfaces on both sides. Nevertheless I can not ping one another. The strange thing is the ping request clearly does invoke any of the net_device_ops: static const struct net_device_ops l4shmnet_netdev_ops = { .ndo_open = l4x_l4shmc_open, .ndo_start_xmit = l4x_l4shmc_xmit_frame, .ndo_stop = l4x_l4shmc_close, .ndo_change_mtu = l4x_l4shmc_change_mtu, .ndo_get_stats = l4x_l4shmc_get_stats, }; I put in all these functions some printk's and I can not see it once the ping starts. I also did with -I option like: ping 192.168.1.2 -I eth0 but still no success. Do You have any idea? Best Regards, Hi, Am 07.02.2014 15:22, schrieb Ajith Whowe: >* Dear Adam, *>>* Thank You very much for the response. Do You mean that the l4shmnet can be used as a communication channel between two (or more ?) instances of l4linux over TCP/IP? * Yes, never tried with more, but two instances are working fine. >* By the way, how should then the start scripts seem? Would it be again like a client - server type interaction between both instances? For instance would it work with the following set up and would I see for example a ping request and response of each side? * The l4shmnet negotiates client and server automatically. l4shmnet needs some namespace to find the other side: - local my_channel = l:new_channel(); + local test_l4shm = l:create_namespace({test_l4shm = "shmns_1"}); >* local linux_caps1 = { *>* log = L4.Env.log:m("rws"); *>* vbus = io_caps.linux_bus1, *>* rtc = rtc_caps.rtc, *>* rom = L4.Env.rom, * - myL4shm = my_channel:svr(), + test_l4shm = test_l4shm:mode("rw"); >* }; *>>* l:start( *>* { *>* caps = linux_caps1, *>* }, *>* "rom/vmlinuz1 mem=512M console=ttyLv0 l4shmnet.add=test_l4shm,macpart=01 ramdisk=rom/ramdisk1 root=1:0 ramdisk_size=5000 l4x_rd=rom/ramdisk1 init=/sbin/init"); *>>>* local linux_caps2 = { *>* log = L4.Env.log:m("r"); *>* vbus = io_caps.linux_bus1, *>* rtc = rtc_caps.rtc, *>* rom = L4.Env.rom, * - myL4shm = my_channel, + test_l4shm = test_l4shm:mode("rw"); >* }; *>>* l:start( *>* { *>* caps = linux_caps2, *>* }, *>* "rom/vmlinuz2 mem=512M console=ttyLv0 l4shmnet.add=test_l4shm,macpart=02 ramdisk=rom/ramdisk2 root=1:0 ramdisk_size=5000 l4x_rd=rom/ramdisk2 init=/sbin/init"); *> Do not forget to enable CONFIG_L4_NET_L4SHM Martin

2 1

Re: Network Server Ankh
by Ajith Whowe 07 Feb '14

07 Feb '14

Dear Adam, Thank You very much for the response. Do You mean that the l4shmnet can be used as a communication channel between two (or more ?) instances of l4linux over TCP/IP? By the way, how should then the start scripts seem? Would it be again like a client - server type interaction between both instances? For instance would it work with the following set up and would I see for example a ping request and response of each side? local my_channel = l:new_channel(); local linux_caps1 = { log = L4.Env.log:m("rws"); vbus = io_caps.linux_bus1, rtc = rtc_caps.rtc, rom = L4.Env.rom, myL4shm = my_channel:svr(), }; l:start( { caps = linux_caps1, }, "rom/vmlinuz1 mem=512M console=ttyLv0 l4shmnet.add=test_l4shm,macpart=01 ramdisk=rom/ramdisk1 root=1:0 ramdisk_size=5000 l4x_rd=rom/ramdisk1 init=/sbin/init"); local linux_caps2 = { log = L4.Env.log:m("r"); vbus = io_caps.linux_bus1, rtc = rtc_caps.rtc, rom = L4.Env.rom, myL4shm = my_channel, }; l:start( { caps = linux_caps2, }, "rom/vmlinuz2 mem=512M console=ttyLv0 l4shmnet.add=test_l4shm,macpart=02 ramdisk=rom/ramdisk2 root=1:0 ramdisk_size=5000 l4x_rd=rom/ramdisk2 init=/sbin/init"); Many thanks in advance, Regards, On Thu Feb 06, 2014 at 17:44:58 +0100, Ajith Whowe wrote: >* I coincidentally met the ankh server in the mail archives and could not *>* figure out well what the ankh exactly does. Is it an ethernet server for *>* more than one application running on the fiasco? * Yes, basically a software network switch with an (optional) network driver. >* By the way it is not existing for the newer versions of l4linux. Was it *>* replaced with the l4shmnet? * No, l4shmnet is only between two partners. The driver is there but disabled because it's not working. Adam -- Adam adam at os.inf.tu-dresden.de <http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers> Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 1

Network Server Ankh
by Ajith Whowe 07 Feb '14

07 Feb '14

Dear all, I coincidentally met the ankh server in the mail archives and could not figure out well what the ankh exactly does. Is it an ethernet server for more than one application running on the fiasco? By the way it is not existing for the newer versions of l4linux. Was it replaced with the l4shmnet? Best Regards,

2 1

nothing after make for snapshot
by Emanuel Berg 03 Feb '14

03 Feb '14

I have not been able to install from l4re-snapshot-2013123021.tar.bz2 The toolchain test says everything is fine (though I had to install dialog and doxygen from the repos as well). With 'make setup' I get the dialog, and I can pick between x86-32 (ia32), UX-32, or amd64/x86_64 (or arm, though I didn't test that). I have a 64-bit CPU but it runs a 32-bit Debian Linux. What happens next is whatever I pick, I get l4/, l4linux/, and fiasco/ in obj/. It says I should set the PATH to include bin/, but except for the arm stuff, there is only setup.d/04-setup there to execute (is that it?). Anyway, I did that, and on 'make' it says: make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ =============== Building all L4Re configurations ============ =============== Building all L4Linux configurations =========== =============== Building Image ================================ =============== Build done ==================================== make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021' However, as there is nothing in those directories, nothing happens. -- underground experts united: http://user.it.uu.se/~embe8573

3 6

Data streaming / sharing from client side in an IPC example
by Ajith Whowe 30 Jan '14

30 Jan '14

Dear Martin, thank you very much for the kind answer. The solution You provided worked well. The only concern is as You know the data to be send can not have a greater size than the L4_UTCB_GENERIC_DATA_SIZE (due to UTCB size). So the question is do you have also another solution for larger data streaming? (Off course other than sending the data by means of various blocks with L4_UTCB_GENERIC_DATA_SIZE) Best Regards, Hi, Am 27.01.2014 15:03, schrieb Ajith Whowe: >* Dear all, *>>* I have reviewed available examples for the client server based *>* applications. Unfortunately could not find any example for which a *>* client sends a char array to the server side. Each time the client *>* sends a request and the server shares the data. Would it be possible *>* to find an example for that? *>>* For instance in the streammap example, the clients does the following *>* (writes basic protocal and message tag to the UTCB and waits for the *>* stream from the server would it be possible for the client to perform *>* the stream whereas the server waits for the input?: *>>* s << l4_umword_t *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga1c2c4b3… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga1c2c4b3…>>(Opcode::Do_map) *>* << (l4_addr_t *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>>)addr; *Just insert the following line here: s << "message from client"; >* s << L4::Ipc::Rcv_fpage::mem((l4_addr_t *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>>)addr, *>* L4_PAGESHIFT *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d…>>, *>* 0); *>>* The server on the other hand gets the protocol and base adress and *>* then does the streaming: *>* l4_addr_t *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>> *>* snd_base; *>* ios >> snd_base; *and insert here: unsigned long len; char buf[100]; len = sizeof(buf); ios >> L4::Ipc::Buf_cp_in<char>(buf, len); buf[len]='\0'; printf ("Received from client: %s\n", buf); >* // put something into the page to read it out at the other side *>* snprintf(page_to_map, sizeof(page_to_map), "Hello from the server!"); *>* printf("Sending to client\n"); *>* // send page *>* ios << L4::Ipc::Snd_fpage::mem((l4_addr_t *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>>)page_to_map, *>* L4_PAGESHIFT *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d…>>, *>* L4_FPAGE_RO *>* <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__fpage__api.html#gga5d4f4972… <http://os.inf.tu-dresden.de/L4Re/doc/group__l4__fpage__api.html#gga5d4f4972…>>, *>* snd_base) *>

2 1

l4linux signals SIGSEGV instead of SIGILL and others
by Martin Schröder 27 Jan '14

27 Jan '14

Hi, I have a piece of code running fine on native Linux, but terminating unexpected with SIGSEGV while running on l4linux on the same piece of hardware. The relevant code is in _armv7_neon_probe "vorr q15,q15,q15" (undefined instruction on ARMv5) which normally would throw SIGILL and thus being caught in the caller. With CONFIG_L4_DEBUG_SEGFAULTS enabled, the exception is correctly printed as > CPSR: 6000010 Err: 00100000 > MyApp/171: Undefined instruction at 0007c7e0 with content f26ee1fe, err 00100000 Unfortunately, when I look into l4linux/arch/l4/kernal/signal.c in l4x_deliver_signal(), errcode is not used at all and so IGSEGV will always be sent, regardless of the exceptions. Martin openssl/crypto/armv4cpuid.S: > .global _armv7_neon_probe > .type _armv7_neon_probe,%function > _armv7_neon_probe: > .word 0xf26ee1fe @ vorr q15,q15,q15 > .word 0xe12fff1e @ bx lr > .size _armv7_neon_probe,.-_armv7_neon_probe

2 3

Data streaming / sharing from client side in an IPC example
by Ajith Whowe 27 Jan '14

27 Jan '14

Dear all, I have reviewed available examples for the client server based applications. Unfortunately could not find any example for which a client sends a char array to the server side. Each time the client sends a request and the server shares the data. Would it be possible to find an example for that? For instance in the streammap example, the clients does the following (writes basic protocal and message tag to the UTCB and waits for the stream from the server would it be possible for the client to perform the stream whereas the server waits for the input?: s << l4_umword_t<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga1c2c4b3…> (Opcode::Do_map) << (l4_addr_t<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…> )addr; s << L4::Ipc::Rcv_fpage::mem((l4_addr_t<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>)addr, L4_PAGESHIFT<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d…>, 0); The server on the other hand gets the protocol and base adress and then does the streaming: l4_addr_t<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>snd_base; ios >> snd_base; // put something into the page to read it out at the other side snprintf(page_to_map, sizeof(page_to_map), "Hello from the server!"); printf("Sending to client\n"); // send page ios << L4::Ipc::Snd_fpage::mem((l4_addr_t<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__basic__types.html#ga4087b99…>)page_to_map, L4_PAGESHIFT<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__memory__api.html#gad2f7e71d…> , L4_FPAGE_RO<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__fpage__api.html#gga5d4f4972…>, snd_base)

2 1

Re: [Compilation Error] Given paths must be relative
by Irvanda Kurniadi 24 Jan '14

24 Jan '14

Hi Johan, Thanks for the solution. The problem is really from missing $. regards, Irvanda On Thu, Jan 23, 2014 at 7:18 PM, Johan Dams <johan.dams(a)wrdsystems.co.uk>wrote: > Hi, > > No sure if this will solve your problem, but your line: > > (patsubst $(PKGDIR)/%.c, %.c, $(filter-out > $(PKGDIR)/lib/src/ompi/mca/pml/csum/pml_csum_endpoint.c... > > Is missing the '$' sign at the beginning, i.e, $(patsubst... > > > Best regards, > Johan > > On Thu, 2014-01-23 at 16:34 +0900, Irvanda Kurniadi wrote: > > Hi, > > > > > > I'm trying to port openmpi. I follow libsdl Makefile structure. This > > is my Makefile: > > > > PKGDIR ?= ../.. > > L4DIR ?= $(PKGDIR)/../.. > > > > TARGET = libmpi.a libmpi.so > > > > CONTRIB_INCDIR = libompi > > REQUIRES_LIBS = libc_support_misc l4re_c-util libpthread > > > > SRC_C = $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/attribute/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/class/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/communicator/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/errhandler/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/file/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/group/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/info/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/allocator/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/allocator/basic/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/allocator/bucket/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/bml/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/bml/r2/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/btl/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/btl/ofud/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out > > $(PKGDIR)/lib/src/ompi/mca/btl/openib/btl_openib_failover.c, > > $(wildcard $(PKGDIR)/lib/src/ompi/mca/btl/base/connect/*.c))) > > \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/btl/self/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/btl/sm/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/btl/tcp/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out > > > $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect/btl_openib_connect_rdmacm.c > $(PKGDIR)/lib/src/ompi/mca/bml/openib/connect/btl_openib_connect_sl.c > $(PKGDIR)/lib/src/ompi/mca/bml/openib/connect/btl_openib_connect_xoob.c, > $(wildcard $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect/*.c))) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/basic/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/hierarch/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/inter/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/self/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/sm/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/sync/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/coll/tuned/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/crcp/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/crcp/bkmrk/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/dpm/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/dpm/orte/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/io/based/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/adio/common/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/glue/openmpi/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/mpool/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/mpool/fake/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/mpool/rdma/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/mpool/sm/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/mtl/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/op/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/osc/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/osc/pt2pt/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/osc/rdma/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/base/*.c)) \ > > (patsubst $(PKGDIR)/%.c, %.c, $(filter-out > > $(PKGDIR)/lib/src/ompi/mca/pml/csum/pml_csum_endpoint.c, > > $(wildcard $(PKGDIR)/lib/src/ompi/mca/pml/csum/*.c))) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/cm/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/crcpw/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/ob1/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/v/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/pessimist/*.c)) > > \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pubsub/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/pubsub/orte/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/rcache/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/rcache/vma/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/topo/base/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mca/topo/unity/*.c)) \ > > lib/src/ompi/mpi/c/attr_fn.c \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/mpi/c/profile/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/op/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/proc/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/request/*.c)) \ > > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > > $(PKGDIR)/lib/src/ompi/runtime/*.c)) > > > > PRIVATE_INCDIR = $(PKGDIR)/lib/src/ompi/attribute/ \ > > $(PKGDIR)/lib/src/ompi/class \ > > $(PKGDIR)/lib/src/ompi/communictor \ > > $(PKGDIR)/lib/src/ompi/errhandler \ > > $(PKGDIR)/lib/src/ompi/file \ > > $(PKGDIR)/lib/src/ompi/group \ > > $(PKGDIR)/lib/src/ompi/info \ > > $(PKGDIR)/lib/src/ompi/mca/allocator/base \ > > $(PKGDIR)/lib/src/ompi/mca/allocator/basic \ > > $(PKGDIR)/lib/src/ompi/mca/allocator/bucket > > \ > > $(PKGDIR)/lib/src/ompi/mca/bml/base \ > > $(PKGDIR)/lib/src/ompi/mca/bml/r2 \ > > $(PKGDIR)/lib/src/ompi/mca/btl/base \ > > $(PKGDIR)/lib/src/ompi/mca/btl/ofud \ > > $(PKGDIR)/lib/src/ompi/mca/btl/openib \ > > > > $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect \ > > $(PKGDIR)/lib/src/ompi/mca/btl/self \ > > $(PKGDIR)/lib/src/ompi/mca/btl/sm \ > > $(PKGDIR)/lib/src/ompi/mca/btl/tcp \ > > $(PKGDIR)/lib/src/ompi/mca/coll/base \ > > $(PKGDIR)/lib/src/ompi/mca/coll/basic \ > > $(PKGDIR)/lib/src/ompi/mca/coll/hierarch \ > > $(PKGDIR)/lib/src/ompi/mca/coll/inter \ > > $(PKGDIR)/lib/src/ompi/mca/coll/self \ > > $(PKGDIR)/lib/src/ompi/mca/coll/sm \ > > $(PKGDIR)/lib/src/ompi/mca/coll/sync \ > > $(PKGDIR)/lib/src/ompi/mca/coll/tuned \ > > $(PKGDIR)/lib/src/ompi/mca/crcp/base \ > > $(PKGDIR)/lib/src/ompi/mca/crcp/bkmrk \ > > $(PKGDIR)/lib/src/ompi/mca/dpm/base \ > > $(PKGDIR)/lib/src/ompi/mca/dpm/orte \ > > $(PKGDIR)/lib/src/ompi/mca/io/base \ > > > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/adio/common \ > > > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io \ > > > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/glue/openmpi > > \ > > $(PKGDIR)/lib/src/ompi/mca/mpool/base \ > > $(PKGDIR)/lib/src/ompi/mca/mpool/fake \ > > $(PKGDIR)/lib/src/ompi/mca/mpool/rdma \ > > $(PKGDIR)/lib/src/ompi/mca/mpool/sm \ > > $(PKGDIR)/lib/src/ompi/mca/mtl/base \ > > $(PKGDIR)/lib/src/ompi/mca/op/base \ > > $(PKGDIR)/lib/src/ompi/mca/osc/base \ > > $(PKGDIR)/lib/src/ompi/mca/osc/pt2pt \ > > $(PKGDIR)/lib/src/ompi/mca/osc/rdma \ > > $(PKGDIR)/lib/src/ompi/mca/pml/base \ > > $(PKGDIR)/lib/src/ompi/mca/pml/cm \ > > $(PKGDIR)/lib/src/ompi/mca/pml/crcpw \ > > $(PKGDIR)/lib/src/ompi/mca/pml/csum \ > > $(PKGDIR)/lib/src/ompi/mca/pml/ob1 \ > > $(PKGDIR)/lib/src/ompi/mca/pml/v \ > > > > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/base \ > > > > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/pessimist \ > > $(PKGDIR)/lib/src/ompi/mca/pubsub/base \ > > $(PKGDIR)/lib/src/ompi/mca/pubsub/orte \ > > $(PKGDIR)/lib/src/ompi/mca/rcache/base \ > > $(PKGDIR)/lib/src/ompi/mca/rcache/vma \ > > $(PKGDIR)/lib/src/ompi/mca/topo/base \ > > $(PKGDIR)/lib/src/ompi/mca/topo/unity \ > > $(PKGDIR)/lib/src/ompi/mpi/c \ > > $(PKGDIR)/lib/src/ompi/mpi/c/profile \ > > $(PKGDIR)/lib/src/ompi/op \ > > $(PKGDIR)/lib/src/ompi/proc \ > > $(PKGDIR)/lib/src/ompi/request \ > > $(PKGDIR)/lib/src/ompi/runtime > > > > > > vpath %.c $(PKGDIR) > > > > include $(L4DIR)/mk/lib.mk > > > > CFLAGS := $(filter-out -Wextra -Wall -Wstrict-prototypes > > -Wmissing-prototypes -Wmissing-declarations,$(CFLAGS)) > > > > > > > > Then, I got this error message: > > > > "given paths must be relative" > > > > > > I can't figure out what is wrong with my Makefile. If you notice > > something, please let me know. Thank you > > > > > > regards, > > > > Irvanda > > > > _______________________________________________ > > l4-hackers mailing list > > l4-hackers(a)os.inf.tu-dresden.de > > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > -- > > PGP Public Key: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x08EDE1CD977FD2AB >

1 0

[Compilation Error] Given paths must be relative
by Irvanda Kurniadi 23 Jan '14

23 Jan '14

Hi, I'm trying to port openmpi. I follow libsdl Makefile structure. This is my Makefile: PKGDIR ?= ../.. > L4DIR ?= $(PKGDIR)/../.. > > TARGET = libmpi.a libmpi.so > > CONTRIB_INCDIR = libompi > REQUIRES_LIBS = libc_support_misc l4re_c-util libpthread > > SRC_C = $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/attribute/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/class/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/communicator/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/errhandler/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/file/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/group/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/info/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/allocator/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/allocator/basic/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/allocator/bucket/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/bml/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/bml/r2/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/ofud/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out > $(PKGDIR)/lib/src/ompi/mca/btl/openib/btl_openib_failover.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/base/connect/*.c))) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/self/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/sm/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/btl/tcp/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out > $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect/btl_openib_connect_rdmacm.c > $(PKGDIR)/lib/src/ompi/mca/bml/openib/connect/btl_openib_connect_sl.c > $(PKGDIR)/lib/src/ompi/mca/bml/openib/connect/btl_openib_connect_xoob.c, > $(wildcard $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect/*.c))) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/basic/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/hierarch/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/inter/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/self/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/sm/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/sync/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/coll/tuned/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/crcp/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/crcp/bkmrk/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/dpm/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/dpm/orte/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/io/based/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/adio/common/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/glue/openmpi/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/mpool/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/mpool/fake/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/mpool/rdma/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/mpool/sm/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/mtl/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/op/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/osc/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/osc/pt2pt/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/osc/rdma/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/base/*.c)) \ > (patsubst $(PKGDIR)/%.c, %.c, $(filter-out > $(PKGDIR)/lib/src/ompi/mca/pml/csum/pml_csum_endpoint.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/csum/*.c))) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/cm/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/crcpw/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/ob1/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/v/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/pessimist/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pubsub/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/pubsub/orte/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/rcache/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/rcache/vma/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/topo/base/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mca/topo/unity/*.c)) \ > lib/src/ompi/mpi/c/attr_fn.c \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/mpi/c/profile/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/op/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/proc/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/request/*.c)) \ > $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard > $(PKGDIR)/lib/src/ompi/runtime/*.c)) > > PRIVATE_INCDIR = $(PKGDIR)/lib/src/ompi/attribute/ \ > $(PKGDIR)/lib/src/ompi/class \ > $(PKGDIR)/lib/src/ompi/communictor \ > $(PKGDIR)/lib/src/ompi/errhandler \ > $(PKGDIR)/lib/src/ompi/file \ > $(PKGDIR)/lib/src/ompi/group \ > $(PKGDIR)/lib/src/ompi/info \ > $(PKGDIR)/lib/src/ompi/mca/allocator/base \ > $(PKGDIR)/lib/src/ompi/mca/allocator/basic \ > $(PKGDIR)/lib/src/ompi/mca/allocator/bucket \ > $(PKGDIR)/lib/src/ompi/mca/bml/base \ > $(PKGDIR)/lib/src/ompi/mca/bml/r2 \ > $(PKGDIR)/lib/src/ompi/mca/btl/base \ > $(PKGDIR)/lib/src/ompi/mca/btl/ofud \ > $(PKGDIR)/lib/src/ompi/mca/btl/openib \ > $(PKGDIR)/lib/src/ompi/mca/btl/openib/connect \ > $(PKGDIR)/lib/src/ompi/mca/btl/self \ > $(PKGDIR)/lib/src/ompi/mca/btl/sm \ > $(PKGDIR)/lib/src/ompi/mca/btl/tcp \ > $(PKGDIR)/lib/src/ompi/mca/coll/base \ > $(PKGDIR)/lib/src/ompi/mca/coll/basic \ > $(PKGDIR)/lib/src/ompi/mca/coll/hierarch \ > $(PKGDIR)/lib/src/ompi/mca/coll/inter \ > $(PKGDIR)/lib/src/ompi/mca/coll/self \ > $(PKGDIR)/lib/src/ompi/mca/coll/sm \ > $(PKGDIR)/lib/src/ompi/mca/coll/sync \ > $(PKGDIR)/lib/src/ompi/mca/coll/tuned \ > $(PKGDIR)/lib/src/ompi/mca/crcp/base \ > $(PKGDIR)/lib/src/ompi/mca/crcp/bkmrk \ > $(PKGDIR)/lib/src/ompi/mca/dpm/base \ > $(PKGDIR)/lib/src/ompi/mca/dpm/orte \ > $(PKGDIR)/lib/src/ompi/mca/io/base \ > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/adio/common \ > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io \ > > $(PKGDIR)/lib/src/ompi/mca/io/romio/romio/mpi-io/glue/openmpi \ > $(PKGDIR)/lib/src/ompi/mca/mpool/base \ > $(PKGDIR)/lib/src/ompi/mca/mpool/fake \ > $(PKGDIR)/lib/src/ompi/mca/mpool/rdma \ > $(PKGDIR)/lib/src/ompi/mca/mpool/sm \ > $(PKGDIR)/lib/src/ompi/mca/mtl/base \ > $(PKGDIR)/lib/src/ompi/mca/op/base \ > $(PKGDIR)/lib/src/ompi/mca/osc/base \ > $(PKGDIR)/lib/src/ompi/mca/osc/pt2pt \ > $(PKGDIR)/lib/src/ompi/mca/osc/rdma \ > $(PKGDIR)/lib/src/ompi/mca/pml/base \ > $(PKGDIR)/lib/src/ompi/mca/pml/cm \ > $(PKGDIR)/lib/src/ompi/mca/pml/crcpw \ > $(PKGDIR)/lib/src/ompi/mca/pml/csum \ > $(PKGDIR)/lib/src/ompi/mca/pml/ob1 \ > $(PKGDIR)/lib/src/ompi/mca/pml/v \ > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/base \ > $(PKGDIR)/lib/src/ompi/mca/pml/v/mca/vprotocol/pessimist > \ > $(PKGDIR)/lib/src/ompi/mca/pubsub/base \ > $(PKGDIR)/lib/src/ompi/mca/pubsub/orte \ > $(PKGDIR)/lib/src/ompi/mca/rcache/base \ > $(PKGDIR)/lib/src/ompi/mca/rcache/vma \ > $(PKGDIR)/lib/src/ompi/mca/topo/base \ > $(PKGDIR)/lib/src/ompi/mca/topo/unity \ > $(PKGDIR)/lib/src/ompi/mpi/c \ > $(PKGDIR)/lib/src/ompi/mpi/c/profile \ > $(PKGDIR)/lib/src/ompi/op \ > $(PKGDIR)/lib/src/ompi/proc \ > $(PKGDIR)/lib/src/ompi/request \ > $(PKGDIR)/lib/src/ompi/runtime > > > vpath %.c $(PKGDIR) > > include $(L4DIR)/mk/lib.mk > > CFLAGS := $(filter-out -Wextra -Wall -Wstrict-prototypes > -Wmissing-prototypes -Wmissing-declarations,$(CFLAGS)) > Then, I got this error message: "given paths must be relative" I can't figure out what is wrong with my Makefile. If you notice something, please let me know. Thank you regards, Irvanda

2 1

Snapshot 2013123012 possible broken for ARM9 & l4linux?
by Martin Schröder 20 Jan '14

20 Jan '14

When I compile the latest l4re-snapshot-2013123021 for ARM Platform (arm-rv-arm9 / Realview ARM9) and run it on qemu (or a real hardware), it stops here: l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=02362f1c l4linux | phys=02000000 ephys=02362f1c l4linux | f_sz=002de3b6 memsz=00362f1c flgs=rwx l4linux | PH 1 (t: 4) offs=002a23ec vaddr=0229a3ec vend=0229a410 l4linux | phys=0229a3ec ephys=0229a410 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002a8, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa800078c l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.12.0-l4 (mschroeder@vm-ms) (gcc version 4.6.2 (OSELAS.Toolchain-2011.11.3) ) #1 Tue Jan 14 16:44:06 CET 2014 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 022b8000 [2784kB] (a bit longer) l4linux | Data: 022b8000 - 022d9200 [132kB] l4linux | Initdata: 0229b000 - 022b723c [112kB] l4linux | BSS: 022de3b6 - 02362f1c [530kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:022b9fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3551232 l4linux | section-with-init: Virt: 0x2000000 to 0x2362f1b [3467 KiB] l4linux | section-with-init: Phys: 0x00250000 to 0x005b2f1b, [3467 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x01900000 to 0x058fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3551232 l4linux | text: Virt: 0x2000000 to 0x2362f1b [3467 KiB] l4linux | text: Phys: 0x00250000 to 0x005b2f1b, [3467 KiB] l4linux | Non-resolvable page fault at 51, ip 20804cc. l4linux | Page fault (non-resolved): pfa=51 pc=20804cc l4linux | Non-resolvable page fault at 56, ip 20804cc. l4linux | panic: going to sleep forever, bye The previous snapshot 2013091917 worked fine. Martin

2 5

GI Operating Systems Meeting
by Björn Döbel 17 Jan '14

17 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, GI, the German Society of Informatics, comprises a Special Interest Group on Operating Systems, which is meeting twice a year to discuss their current research work. The next meeting will be hosted by TU Dresden in May 2014. Please consider submitting a talk. Title: Secure and Reliable Operating Systems Date: May 22/23 2014, TU Dresden, Dept. of Computer Science Computer systems are an indispensable part of daily life. We can no longer avoid to trust these systems with private data, confidential business information, and even our lives. Therefore, this meeting will focus on operating system mechanisms that enable these systems to provide reliability and security. You are cordially invited to submit talks that address design and implementation of dependable and secure operating systems and runtime environments. These topics include (amongst others): * Design of dependable operating system kernels * Secure application architectures * Infrastructures for Cloud Computing * Secure and dependable embedded systems * Tool support for operating system development Please send an abstract for your talk until March 31st 2014 to Björn Döbel (doebel(a)os.inf.tu-dresden.de). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlLY8SgACgkQP5ijxgQLUNk5+ACdHXk4O9fyWtdIkZiAL1sug8xP 8IoAn13iFztObmch50/cp0NImShxpsD6 =MjQ1 -----END PGP SIGNATURE-----

1 0

Re: [ASK] Unable to boot L4 + Fiasco using u-boot in pandaboard
by Wei Jin 17 Jan '14

17 Jan '14

I'm sorry it doesn't help. There isn't a pandaboard available for me now so I'm unable to test it. I'll get one asap. Anyway here is my uimage of the hello example. bootstrap_hello.uimage<https://docs.google.com/file/d/0B18xNzfFopc9OVdjdTRQZjhLMkE/edit?usp=drive_…> On Fri, Jan 17, 2014 at 7:20 AM, Erry Pradana Darajati < pradana.erry(a)gmail.com> wrote: > It still didn't boot in my pandaboard. I am using Pandaboard ES B1. > in my boot partition there are MLO, u-boot.bin and bootstrap.uimage -> > uImage from L4 build > any idea why ? > Or maybe, if i'm not so rude. May i see your bootstrap.uimage ? Just for a > comparison > Thank you very much Jin > > > 2014/1/17 Wei Jin <coder.soap(a)gmail.com> > >> You need to rename it ''uImage''. >> Actually boot.scr is not needed. Just these two files are enough. >> >> >> On Fri, Jan 17, 2014 at 2:41 AM, Erry Pradana Darajati < >> pradana.erry(a)gmail.com> wrote: >> >>> Thank you, for your help Jin >>> I want to ask you one more thing. >>> After i copy these two file i must copy bootstrap.uimage to boot >>> partition right ? >>> And then i need to create boot.scr ? >>> Again, i really thank you for helping me >>> >>> >>> 2014/1/16 Wei Jin <coder.soap(a)gmail.com> >>> >>>> Hi! >>>> >>>> Uboot-L4.zip<https://docs.google.com/file/d/0B18xNzfFopc9Q0h0ZXh2YTNpMzA/edit?usp=drive_…> >>>> Please try this one. At least it works for me. >>>> >>>> >>>> On Thu, Jan 16, 2014 at 7:14 PM, Erry Pradana Darajati < >>>> pradana.erry(a)gmail.com> wrote: >>>> >>>>> After searching in the net, i found the way to make u-boot and how to >>>>> install it. But i encounter some problem >>>>> After copy u-boot.img, MLO, and boot.scr in the first partition of my >>>>> SDCard. The site said that it the u-boot should be booting my uimage. But >>>>> in reality my Pandaboard is not responding (as if there are no SDCard >>>>> inserted) >>>>> I follow the instructions from elinux.org ( >>>>> http://elinux.org/Panda_How_to_MLO_%26_u-boot) and other source that >>>>> give same instructions like elinux.org >>>>> Can you tell me what i'm doing wrong ? >>>>> Thank you for the answer, I am really appreciate any help and answer >>>>> >>>>> -- >>>>> *Regards,* >>>>> *Erry Pradana Darajati | Student of Computer Engineering* >>>>> *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia* >>>>> >>>>> _______________________________________________ >>>>> l4-hackers mailing list >>>>> l4-hackers(a)os.inf.tu-dresden.de >>>>> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >>>>> >>>>> >>>> >>> >>> >>> -- >>> *Regards,* >>> *Erry Pradana Darajati | Student of Computer Engineering* >>> *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia* >>> >> >> > > > -- > *Regards,* > *Erry Pradana Darajati | Student of Computer Engineering* > *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia* >

1 0

Re: [ASK] Unable to boot L4 + Fiasco using u-boot in pandaboard
by Wei Jin 16 Jan '14

16 Jan '14

You need to rename it ''uImage''. Actually boot.scr is not needed. Just these two files are enough. On Fri, Jan 17, 2014 at 2:41 AM, Erry Pradana Darajati < pradana.erry(a)gmail.com> wrote: > Thank you, for your help Jin > I want to ask you one more thing. > After i copy these two file i must copy bootstrap.uimage to boot partition > right ? > And then i need to create boot.scr ? > Again, i really thank you for helping me > > > 2014/1/16 Wei Jin <coder.soap(a)gmail.com> > >> Hi! >> >> Uboot-L4.zip<https://docs.google.com/file/d/0B18xNzfFopc9Q0h0ZXh2YTNpMzA/edit?usp=drive_…> >> Please try this one. At least it works for me. >> >> >> On Thu, Jan 16, 2014 at 7:14 PM, Erry Pradana Darajati < >> pradana.erry(a)gmail.com> wrote: >> >>> After searching in the net, i found the way to make u-boot and how to >>> install it. But i encounter some problem >>> After copy u-boot.img, MLO, and boot.scr in the first partition of my >>> SDCard. The site said that it the u-boot should be booting my uimage. But >>> in reality my Pandaboard is not responding (as if there are no SDCard >>> inserted) >>> I follow the instructions from elinux.org ( >>> http://elinux.org/Panda_How_to_MLO_%26_u-boot) and other source that >>> give same instructions like elinux.org >>> Can you tell me what i'm doing wrong ? >>> Thank you for the answer, I am really appreciate any help and answer >>> >>> -- >>> *Regards,* >>> *Erry Pradana Darajati | Student of Computer Engineering* >>> *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia* >>> >>> _______________________________________________ >>> l4-hackers mailing list >>> l4-hackers(a)os.inf.tu-dresden.de >>> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >>> >>> >> > > > -- > *Regards,* > *Erry Pradana Darajati | Student of Computer Engineering* > *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia* >

1 0

Problem with given root-x86-gingerbread.img
by Viswa Sekar 16 Jan '14

16 Jan '14

Now that L4 android boots but it stands up in Black screen saying ANDROID_ and then after some time it turns into a complete black screen. This is what i did 1. l4 re and fiasco are to be used only with revision 40. (it doesnt work for other revisions) 2. Downloaded l4android snapshot version 3.5 3. Compiled everything for x86 architecture as per instructions given in the respective websites. 4. For l4 android compilation, building, i used the pre built images given in the website, and did a manual build for ISO image got the iso, vmlinuz.android files built successfully. Now in the final step: when i tried booting the l4android over l4re, i get a black screen. booting and saying ANDROID_. Later then I downloaded the DEMO image for l4android given in the website. I mounted into my PC and opened the ISO folder. After trial and error method of replacing the vmlinuz, and image files like system, root, I found that replacing the root-x86-gingerbread.img from the ISO to the one that is given in the l4andoid website (pre built images) makes the system boot, and android successfully boots. (i.e) i copied root-x86_gingerbread.img from DEMO image`s folder to my project directory and used instead of the one specified in website ( it boots only for changing the root not system-x86.img) Can you please explain me what is the problem, that has occurred? is it that the root-x86_gingerbread.img file given in the website outdated? or kindly give your suggestion. The below is the output that i got when i used root-x86_gingerbread.img -> downloaded from the l4android website. Why does it stand in Black screen though it is booted? OUTPUT: viswa@atmvs17:~/Documents/final/l4/mybuild$ qemu-system-i386 -cdrom /home/viswa/Documents/final/l4/mybuild/images/l4_gingerbread-x86.iso -serial stdio -m 512 -boot d L4 Bootstrapper Build: #1 Mon Jan 13 11:21:39 CET 2014, x86-32, 4.6.1 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 000000001fffcfff: 523252kB Total RAM: 511MB Moving modules behind 1100000 moving module 00 { 138000-1a25ff } -> { 839e000-84085ff } [435712] moving module 01 { 1a3000-1f7784 } -> { 8409000-845d784 } [345989] moving module 02 { 2e4000-5176aa } -> { 845e000-86916aa } [2307755] moving module 03 { 518000-639390 } -> { 73d6000-74f7390 } [1184657] moving module 04 { 63a000-86e2e9 } -> { 74f8000-772c2e9 } [2310890] moving module 05 { 86f000-1276b7c } -> { 772d000-8134b7c } [10517373] moving module 09 { 2b4000-2b47a3 } -> { 1100000-11007a3 } [1956] moving module 10 { 2a9000-2a93b6 } -> { 1101000-11013b6 } [951] moving module 11 { 2cf000-2cf617 } -> { 1102000-1102617 } [1560] moving module 06 { 1277000-137c6cf } -> { 1103000-12086cf } [1070800] moving module 07 { 137d000-176ec36 } -> { 1209000-15fac36 } [4135991] moving module 08 { 176f000-18e6b80 } -> { 15fb000-1772b80 } [1538945] moving module 12 { 18e7000-1c6183b } -> { 1773000-1aed83b } [3647548] moving module 13 { 1c62000-1d61fff } -> { 1aee000-1bedfff } [1048576] moving module 14 { 1d62000-73d5fff } -> { 1bee000-7261fff } [90652672] moving module 03 { 73d6000-74f7390 } -> { 7262000-7383390 } [1184657] moving module 04 { 74f8000-772c2e9 } -> { 7384000-75b82e9 } [2310890] moving module 05 { 772d000-8134b7c } -> { 75b9000-7fc0b7c } [10517373] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/l4_gingerbread-x86.cfg Bootloader MMAP: [ 0, 9f400) RAM (1) [ 9f400, a0000) reserved (2) [ f0000, 100000) reserved (2) [ 100000, 1fffd000) RAM (1) [ 1fffd000, 20000000) reserved (2) [ feffc000, ff000000) reserved (2) [ fffc0000, 100000000) reserved (2) Relocated mbi to [0x2df000-0x2df511] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 9f400, 9ffff] { c00} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10b197] { b198} Sigma0 sigma0 [ 140000, 18d25f] { 4d260} Root moe [ 2d0000, 2e3427] { 13428} Boot bootstrap [ 2df000, 2df60e] { 60f} Root Multiboot info [ 300000, 38ffff] { 90000} Kern fiasco [ 400000, 46ffff] { 70000} Kern fiasco [ 1100000, 7fc0b7c] { 6ec0b7d} Root Module [ 1fffd000, 1fffffff] { 3000} Arch BIOS [ feffc000, feffffff] { 4000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001dc sp:002de070 Roottask config ip:001401c4 sp:00000000 Starting kernel fiasco at 00300888 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2012 TU Dresden Rev: r40 compiled with gcc 4.6.1 for Intel Pentium Pro [] Build: #1 Mon Jan 13 11:04:27 CET 2014 Performance-critical config option(s) detected: CONFIG_NDEBUG is off Superpages: yes Kmem:: cpu page at 1fff8000 (4096Bytes) ACPI-Init ACPI: RSDP[0xfdab0] r00 OEM:BOCHS. ACPI: RSDT[0x203fd6a0] r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ffe70] r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203fd800] r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203fd720] r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203fd6e0] r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203fd720 IO-APIC[ 0]: struct: 0x203fd754 adr=fec00000 Boot_alloc: size=0x1c Boot_alloc: allocated extra memory block @0xfeffb000 (size=400) Boot_alloc: @ 0xfeffb000 Boot_alloc: remaining free block @ 0xfeffb020 (size=3e0) Boot_alloc: size=0x120 Boot_alloc: @ 0xfeffb020 Boot_alloc: remaining free block @ 0xfeffb140 (size=2c0) IO-APIC[ 0]: pins 24 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 IO-APIC: ovr[ 1] 05 -> 5 IO-APIC: ovr[ 2] 09 -> 9 IO-APIC: ovr[ 3] 0a -> a IO-APIC: ovr[ 4] 0b -> b Boot_alloc: size=0x4 Boot_alloc: @ 0xfeffb140 Boot_alloc: remaining free block @ 0xfeffb148 (size=2b8) Allocate cpu_mem @ 0xfeffb400 FPU0: SSE Local APIC[00]: version=14 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Boot_alloc: size=0x14 Boot_alloc: @ 0xfeffb148 Boot_alloc: remaining free block @ 0xfeffb160 (size=2a0) Boot_alloc: size=0x300 Boot_alloc: allocated extra memory block @0xfeffb800 (size=400) Boot_alloc: @ 0xfeffb800 Boot_alloc: remaining free block @ 0xfeffbb00 (size=100) Enable MSI support: chained IRQ mgr @ 0xfeffb140 Absolute KIP Syscalls using: Sysenter CPU[0:0]: GenuineIntel (6:3:3:0)[00000633] Model: QEMU Virtual CPU version 0.14.1 at 2394 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 28672 bytes (7 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:1000;9efff] [0:10c000;13ffff] [4:140000;18dfff] [0:18e000;2defff] [4:2df000;2dffff] [0:2e0000;3fffff] [0:469000;10fffff] [4:1100000;7fc0fff] [0:7fc1000;1d70efff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:1fffd000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 367776 KByte free memory MOE: found RAM from 1000 to 1d70f000 MOE: allocated 471 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [7262000-7383391] [C:503000] l4re BOOTFS: [7384000-75b82ea] [C:504000] ned BOOTFS: [75b9000-7fc0b7d] [C:505000] io BOOTFS: [1103000-12086d0] [C:506000] rtc BOOTFS: [1209000-15fac37] [C:507000] mag BOOTFS: [15fb000-1772b81] [C:508000] fb-drv BOOTFS: [1100000-11007a4] [C:509000] l4_gingerbread-x86.cfg BOOTFS: [1101000-11013b7] [C:50a000] x86-legacy.devs BOOTFS: [1102000-1102618] [C:50b000] l4_android-x86.vbus BOOTFS: [1773000-1aed83c] [C:50c000] vmlinuz.android BOOTFS: [1aee000-1bee000] [C:50d000] root-x86-ginger.img BOOTFS: [1bee000-7262000] [C:50e000] system-x86-ginger.img No fpage received MOE: cmdline: moe rom/l4_gingerbread-x86.cfg MOE: Starting: rom/ned rom/l4_gingerbread-x86.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4_gingerbread-x86.cfg' io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | GTF: register factory for N2Hw12Msi_resourceE io | GTF: register factory for 7Pci_dev io | Dev_factory: register factory for N2Hw6DeviceE io | Io service io | Find root Pointer io | Find root Pointer: fdab0 io | ACPI: RSDP 0xfdab0 00014 (v00 BOCHS ) io | ACPI: RSDT 0x1fffd6a0 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x1ffffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x1fffd8a0 02560 (v01 BXPC BXDSDT 00000001 INTL 20100528) io | ACPI: FACS 0x1ffffe00 00040 io | ACPI: SSDT 0x1fffd800 0009E (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x1fffd720 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x1fffd6e0 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 381 Objects with 77 Devices 118 Methods 7 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 8 Objects with 0 Devices 4 Methods 0 Regions io | tbxface-0601 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0184 [02] Enable : Transition to ACPI mode successful io | evgpeblk-1129 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | /home/viswa/Documents/final/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:57:AcpiOsInstallInterruptHandler: UNINPLEMENTED io | Completing Region/Field/Buffer/Package initialization:.................... io | Initialized 7/7 Regions 0/0 Fields 8/8 Buffers 5/5 Packages (398 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 0 _STA executions (examined 80 objects) io | evgpeblk-1234 [03] EvInitializeGpeBlock : Found 0 Wake, Enabled 16 Runtime GPEs in this block io | ACPICA-Version:20091214, System in ACPI MODE, 32bit timer io | Ready. Waiting for request. mag | Hello from MAG fb | Trying execution of ``set VBE mode'' using x86emu fb | Found VESA BIOS version 2.0 fb | OEM VGABIOS Cirrus extension fb | VBE mode 0x117 successfully set. fb | Framebuffer memory: phys: f0000000 - f0400000 fb | virt: 400000 - 800000 fb | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 pos: 0, 0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 400000-800000 mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 mag | Plugin: Frame-buffer service started mag | Plugin: Mag_client service started android | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=00685000 android | phys=00400000 ephys=00685000 android | f_sz=00285000 memsz=00285000 flgs=r-x android | PH 1 (t: 1) offs=00286000 vaddr=00685000 vend=0077d000 android | phys=00685000 ephys=0077d000 android | f_sz=0004aa2c memsz=000f8000 flgs=rw- android | PH 2 (t: 4) offs=001fe99c vaddr=005fd99c vend=005fd9c0 android | phys=005fd99c ephys=005fd9c0 android | f_sz=00000024 memsz=00000024 flgs=--- android | Starting binary at 0x400000, argc=16 argv=0x80007f68 *argv=0xb1007fec argv0=rom/vmlinuz.android android | External resolver is at 0xa80006d0 android | ======> L4Linux starting... <======== android | Linux version 3.5.0-l4 (viswa@atmvs17) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 Mon Jan 13 12:42:11 CET 2014 android | Binary name: rom/vmlinuz.android android | Linux kernel command line (15 args): console=ttyLv0 mem=256M l4bdds.add=rom/system-x86-ginger.img,rw androidboot.console=ttyLv0 boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-x86-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreen=1 androidboot.hardware=l4 android | CPU mapping (l:p)[1]: 0:0 android | Image: 00400000 - 0077d000 [3572 KiB]. android | Areas: Text: 00400000 - 00685000 [2580kB] (a bit longer) android | Data: 00685000 - 006a8540 [141kB] android | Initdata: 006a9000 - 006d0000 [156kB] android | BSS: 006d0000 - 0076d000 [628kB] android | gs=43 fs=43 android | Device scan: android | Device: (noname) android | Device: PCI0 android | Device scan done. android | l4x_fiasco_gdt_entry_offset = 9 rtc | Date:13.01.2014 Time:14:27:51 android | l4lx_thread_create: Created thread 418 (cpu0) (u:b3000e00, v:b3000c00, sp:00687ff8) android | main thread will be 418 android | l4x_register_pointer_section: addr = 00685000 size = 1015808 android | section-with-init: virt: 0x685000 to 0x77cfff [992 KiB] android | section-with-init: Phys: 0x00974000 to 0x00a6c000, Size: 1015808 android | Main thread running, waiting... android | WARNING: Unknown wrmsr: 0000008b at 0x6bf130 android | l4x_setup_memory: Forcing superpages for main memory android | l4re_global_env: 0xb1007e24 android | Main memory size: 256MB android | Main memory: virt: 0x800000 to 0x107fffff [262144 KiB] android | Main memory: Phys: 0x08000000 to 0x18000000, Size: 268435456 android | Filling lower ptabs... android | Done (1153 entries). android | l4x_register_pointer_section: addr = 00400000 size = 2641920 android | text: virt: 0x400000 to 0x684fff [2580 KiB] android | text: Phys: 0x00659000 to 0x008de000, Size: 2641920 android | l4x_rd_path: rom/root-x86-ginger.img android | Loading: rom/root-x86-ginger.img android | INITRD: Size of RAMdisk is 1024KiB android | RAMdisk from 1891b000 to 18a1b000 [1024KiB] Linux version 3.5.0-l4 (viswa@atmvs17) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #1 Mon Jan 13 12:42:11 CET 2014 e820: BIOS-provided physical RAM map: L4Lx-Memory: [mem 0x0000000000000000-0x00000000003fffff] reserved L4Lx-Memory: [mem 0x0000000000400000-0x000000000077cfff] usable L4Lx-Memory: [mem 0x000000000077d000-0x00000000007fffff] unusable L4Lx-Memory: [mem 0x0000000000800000-0x00000000107fffff] usable Notice: NX (Execute Disable) protection missing in CPU! e820: last_pfn = 0x10800 max_arch_pfn = 0x100000 init_memory_mapping: [mem 0x00000000-0x107fffff] INITRD: 1891b000 - 18a1b000 264MB LOWMEM available. mapped low ram: 0 - 10800000 low ram: 0 - 10800000 Zone ranges: DMA [mem 0x00400000-0xffffffff] Normal [mem 0x00000000-0x107fffff] Movable zone start for each node Early memory node ranges node 0: [mem 0x00400000-0x0077cfff] node 0: [mem 0x00800000-0x107fffff] e820: [mem 0x10800000-0xffffffff] available for PCI devices Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65909 Kernel command line: console=ttyLv0 mem=256M l4bdds.add=rom/system-x86-ginger.img,rw androidboot.console=ttyLv0 boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-x86-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreKernel command line: console=PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) __ex_table already sorted, skipping sort Initializing CPU#0 Memory: 259676k/270336k available (2036k kernel code, 6040k reserved, 684k data, 156k init, 0k highmem) virtual kernel memory layout: fixmap : 0x18901000 - 0x1891b000 ( 104 kB) vmalloc : 0x10800000 - 0x18800000 ( 128 MB) lowmem : 0x00000000 - 0x10800000 ( 264 MB) .init : 0x006a9000 - 0x006d0000 ( 156 kB) .data : virtual kernel memory layout: fixmap : 0x18901000 - 0x1891b000 ( 104 kB) vmNR_IRQS:192 nr_irqs:192 192 Console: colour dummy device 80x25 console [ttyLv0] enabled l4timer: Using IRQ65 android | l4lx_thread_create: Created thread 420 (timer) (u:b3000a00, v:00000000, sp:00707ff4) Detected 2394.021 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 4788.04 BogoMIPS (lpj=23940210) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 android | WARNING: Unknown wrmsr: 0000008b at 0x6bf130 CPU: Intel QEMU Virtual CPU version 0.14.1 stepping 03 Performance Events: android | WARNING: Unknown rdmsr: 00000186 at 0x6afb4f android | WARNING: Unknown rdmsr: 00000187 at 0x6afb4f android | WARNING: Unknown wrmsr: 000000c1 at 0x6afbd0 Broken PMU hardware detected, using software events only. NET: Registered protocol family 16 bio: create slab <bio-0> at 0 Failed to create "l4x" debugfs directory: 1 Advanced Linux Sound Architecture Driver Version 1.0.25. Switching to clocksource l4kipclk NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. platform rtc_cmos: registered platform RTC device (no PNP device found) squashfs: version 4.0 (2009/01/31) Phillip Lougher msgmni has been set to 507 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb.0: looking for capability 'fb' as goos session l4fb l4fb.0: 640x480@16 2bypp, size: 614400 @ 18a00000 l4fb l4fb.0: 5:6:5 11:5:0 linelen=1280 visual=2 l4fb l4fb.0: l4fb L4 frame buffer device (refresh: 10jiffies) Console: switching to colour frame buffer device 80x30 L4 serial driver ttyLv0 at MMIO 0x1 (irq = 64) is a L4 brd: module loaded l4bdds: Disk 'rom/system-x86-ginger.img' size = 88528 KB (86 MB) flags=101 addr=18a96000 l4bdds0: unknown partition table mousedev: PS/2 mouse device common for all mice rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 rtc_cmos rtc_cmos: only 24-hr supported ashmem: initialized logger: created 256K log 'log_main' logger: created 256K log 'log_events' logger: created 256K log 'log_radio' logger: created 256K log 'log_system' TCP: cubic registered NET: Registered protocol family 17 /home/viswa/Documents/final/l4android/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) ALSA device list: #0: Dummy 1 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 1024KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing unused kernel memory: 156k freed init: cannot open '/initlogo.rle' init: Unable to open persistent property directory /data/property errno: 2 init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. init: cannot find '/system/bin/servicemanager', disabling 'servicemanager' init: cannot find '/system/bin/vold', disabling 'vold' init: cannot find '/system/bin/netd', disabling 'netd' init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' init: cannot find '/system/bin/rild', disabling 'ril-daemon' init: cannot find '/system/bin/app_process', disabling 'zygote' init: cannot find '/system/bin/alsa_ctl', disabling 'alsainit' init: cannot find '/system/bin/mediaserver', disabling 'media' init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' init: cannot find '/system/bin/installd', disabling 'installd' init: cannot find '/system/bin/keystore', disabling 'keystore' init: cannot find '/system/bin/powerbtnd', disabling 'powerbtnd' init: cannot find '/system/bin/faketsd', disabling 'faketsd' init: cannot find '/system/bin/sh', disabling 'console' Switching to clocksource tsc Clocksource tsc unstable (delta = 63656760 ns) Switching to clocksource l4kipclk ___________________________________ -- With warm regards, *VISWA SUBRAMANIAN SEKAR* Final Year B.E Computer Science and Engineering PSG COLLEGE OF TECHNOLOGY Coimbatore. Phone: +91 94427 94420 Email: viswasekarsubramanian(a)gmail.com

2 2

[ASK] Unable to boot L4 + Fiasco using u-boot in pandaboard
by Erry Pradana Darajati 16 Jan '14

16 Jan '14

After searching in the net, i found the way to make u-boot and how to install it. But i encounter some problem After copy u-boot.img, MLO, and boot.scr in the first partition of my SDCard. The site said that it the u-boot should be booting my uimage. But in reality my Pandaboard is not responding (as if there are no SDCard inserted) I follow the instructions from elinux.org ( http://elinux.org/Panda_How_to_MLO_%26_u-boot) and other source that give same instructions like elinux.org Can you tell me what i'm doing wrong ? Thank you for the answer, I am really appreciate any help and answer -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Re: Porting libtiff library
by Irvanda Kurniadi 16 Jan '14

16 Jan '14

> > TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > reference in libtiff.so > libuc_c.a: could not read symbols: Bad value > I found the source of the problem. I compiled, assambled, and linked libtiff and libtiff program with different toolchain (libtiff using gcc, libtiff program using uClibc). regards, Irvanda

1 0

Re: Porting libtiff library
by Irvanda Kurniadi 16 Jan '14

16 Jan '14

On Sun, 12 Jan 2014 23:17:12 +0100, Adam Lackorzynski wrote: > > After I ported libtiff library then I tried to compile simple tiff > > program, I found this error: > > > > TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > > reference in libtiff.so > > > > libuc_c.a: could not read symbols: Bad value > > > > > > What does it mean? > > Looks like a shared libtiff is being linked to an otherwise static > program. How does the Makefile of your libtiff program look like? > This is the Makefile of my libtiff program: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. DEPENDS_PKGS = libtiff REQUIRES_LIBS = libtiff TARGET = tiff_test SRC_C = tiff_test.c LDFLAGS = -ltiff include $(L4DIR)/mk/prog.mk regards, Irvanda

1 0

Writing to TTBCR on ARM9 causes fault
by Martin Schröder 14 Jan '14

14 Jan '14

I am trying to get L4 running on the freescale i.MX28 EVK. During startup it stops with a fault at fiasco/src/kern/arm/bootstrap.cpp:236 asm volatile("mcr p15, 0, %[ttbcr], c2, c0, 2" // TTBCR : : [ttbcr] "r" (Page::Ttbcr_bits)); Unlike ARM11, the ARM9 does not know about TTBCR. [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0198e/I10149…] So maybe this might be omitted on ARM9? Martin

2 1

NOVA, NUL, snapshotting
by Sartakov A. Vasily 13 Jan '14

13 Jan '14

Hello. Does the NOVA/NUL support snapshotting of VMes? -- Sartakov A. Vasily

5 21

about the alien thread
by Wei Jin 12 Jan '14

12 Jan '14

Hello! I'm tring to understand how the alien thread works. I'm not confident in what I have got. Please correct me: When an alien thread invokes an IPC call, it raises an exception, which would be caught by the excenption handler as configured. The exception handler could get the status of the alien thread by reading exception regs in UTCB ( l4_utcb_exc<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__utcb__exc__api.html#ga3d957…> () ). The exception handler could also set this IPC call allowed or not. If this IPC call is allowed, the alien thread acts like a non-alien thread the performs the IPC call. // This is what I doubt since the alien example does not provide a valid IPC call. If this IPC call is not allowed, the alien thread executes from where it raise the exception.

2 1

Porting libtiff library
by Irvanda Kurniadi 12 Jan '14

12 Jan '14

Thanks Adam, > >* I've put the revision of jpegv9a and it solved the problem of true and > *>* false. But now I'm having another problem. I compiled libtiff library and > *>* got this error message: > *> >* lib/contrib/contrib/dbs/tiff-bi.s.o: In function `main': > *>* /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-bi.c:36: > *>* multiple definition of `main' > *>* lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: > *>* first defined here > *>* lib/contrib/contrib/dbs/tiff-grayscale.s.o: In function `main': > *>* /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-grayscale.c:42: > *>* multiple definition of `main' > *>* lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: > *>* first defined here > * > I think you included too many files in your Makefile. libtiff also > contains programs (e.g. for testing purposes) which are not part of the > library itself. You must not include those when building the library. > Also, including files with 'win32' in the file name does not seem good > to me. I recommend to only include those files that are part of a > library build on Linux (display with "ar t libtiff.a"). > > After I ported libtiff library then I tried to compile simple tiff program, I found this error: TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > reference in libtiff.so libuc_c.a: could not read symbols: Bad value > What does it mean? I found a solution for the problem which is similar to mine. http://os.inf.tu-dresden.de/pipermail/l4-hackers/2006/002126.html They said,"The errno.h file declares errno as global rather than per-thread, which is bogus on a TLS system. Official fix is to remove that errno.h file completely". But I don't know which errno.h that I should remove. Or maybe you have different solution for this problem? Regards, Irvanda

2 1

Porting libtiff library
by Irvanda Kurniadi 09 Jan '14

09 Jan '14

Thanks Adam, I've put the revision of jpegv9a and it solved the problem of true and false. But now I'm having another problem. I compiled libtiff library and got this error message: lib/contrib/contrib/dbs/tiff-bi.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-bi.c:36: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here lib/contrib/contrib/dbs/tiff-grayscale.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-grayscale.c:42: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here ... ... ... lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here lib/contrib/tools/tiffsplit.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/tools/tiffsplit.c:59: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here make[8]: *** [libtiff.so] Error 1 make[7]: *** [/home/irvanda/l4linux_test/obj/l4/x86/pkg/libtiff/lib/build/OBJ-x86_586] Error 2 make[6]: *** [build] Error 2 make[5]: *** [lib] Error 2 make[4]: *** [libtiff] Error 2 make[3]: *** [pkg] Error 2 make[2]: *** [x] Error 2 ^Cmake[1]: *** [build_all] Interrupt make: *** [all] Interrupt This is my Makefile in build directory: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libtiff.a libtiff.so DEPENDS_PKGS = libjpeg SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) include $(L4DIR)/mk/Makeconf REQUIRES_LIBS = libjpeg zlib CONTRIB_INCDIR = libtiff SRC_C = $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out $(PKGDIR)/lib/contrib/libtiff/tif_win32.c $(PKGDIR)/lib/contrib/libtiff/mkg3states.c, $(wildcard $(PKGDIR)/lib/contrib/libtiff/*.c))) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/addtiffo/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/dbs/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/iptcutil/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/mfs/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/port/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out $(PKGDIR)/lib/contrib/tools/sgi2tiff.c $(PKGDIR)/lib/contrib/tools/sgisv.c $(PKGDIR)/lib/contrib/tools/tiffgt.c $(PKGDIR)/lib/contrib/tools/sgisv.c $(PKGDIR)/lib/contrib/tools/ycbcr.c, $(wildcard $(PKGDIR)/lib/contrib/tools/*.c))) PRIVATE_INCDIR = $(PKGDIR)/lib/contrib/libtiff \ $(PKGDIR)/lib/contrib/contrib/addtiffo \ $(PKGDIR)/lib/contrib/contrib/dbs \ $(PKGDIR)/lib/contrib/contrib/iptcutil \ $(PKGDIR)/lib/contrib/contrib/mfs \ $(PKGDIR)/lib/contrib/port \ $(PKGDIR)/lib/contrib/tools \ vpath %.c $(PKGDIR) include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wimplicit-function-declaration -Wformat,$(CFLAGS)) I hope some of hackers here can help me solving this problem. best regards, Irvanda

2 1

IRQ request from server to client and server.loop()
by cem akpolat 21 Dec '13

21 Dec '13

Dear all, I am quite new to the microkernel concept and I am trying to somehow build an IRQ mechanism between client and server. There are two questions that I want to ask: 1- Is it possible to receive an IRQ message being sent by Server on the client and handle it? I tried to apply that on the shared_ds examples. However what I see is the IRQ registration could be done only on the server side. How can a client, in a shared memory case,receive an IRQ request from server and how can a server send an IRQ request (in other words trigger an IRQ) to the client. 2- How can we remove or disable the server.loop mechanism? What is the role of this function? I appreciate that you can answer these questions. Best regards, Cem

2 7

Error while compiling program in l4re
by Irvanda Kurniadi 20 Dec '13

20 Dec '13

Hi, I was trying to compile my program which contains libtiff and libgomp. But I got this error message when I compiled my program. ld: errno: TLS reference in ..../l4linux_test/obj/l4/x86/lib/x86_586/l4f/libpthread.a(semaphore.o) mismatches non-TLS reference in ..../l4linux_test/obj/l4/x86/lib/x86_586/libtiff.so ..../l4linux_test/obj/l4/x86/lib/x86_586/l4f/libpthread.a: could not read symbols: Bad value Previously, I ported the libtiff library by myself. Is it happen because I didn't port it properly? Regards, Irvanda

1 0

L4RE compile error in file rt_sched-proto.h
by Wei Jin 19 Dec '13

19 Dec '13

Hi all! I got several errors while compiling L4RE(r59). It's about real-time scheduling extension headers in L4RE(file 'pkg/l4sys/ARCH-x86/rt_sched.h', 'pkg/l4sys/ARCH-x86/rt_sched-proto.h'). Here's the mesage: In file included from /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched.h:29:0, from /home/soap/project/L4/l4/pkg/rtdemo/server/src/rtdemo.c:13: /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:30:29: fatal error: l4/sys/syscalls.h: No such file or directory I can't find any header named "syscalls.h" in pkg/l4sys, so I comment it. Then I got more errors: In file included from /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched.h:29:0, from /home/soap/project/L4/l4/pkg/rtdemo/server/src/rtdemo.c:13: /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:57:5: error: unknown type name ‘l4_low_high_t’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:79:16: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘slice’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:105:19: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘slice’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:127:31: error: unknown type name ‘l4_threadid_t’ I can't find the definition of 'l4_low_high_t' and 'l4_threadid_t' in L4RE, but instead I found them in the legacy l4env: typedef struct { l4_umword_t low; l4_umword_t high; } l4_low_high_t; tyoedef union { l4_uint32_t raw; l4_threadid_struct_t id; } l4_threadid_t; Should I define them the same as l4env? The declairation 'L4_INLINE int l4_rt_add_time slice(l4_threadid_t dest, int prio, int time)", which also appears in the online doc( http://os.inf.tu-dresden.de/L4Re/doc/group__api__calls__rt__sched.html), seems strange. Is it a typo? "l4_rt_add_time_slice" seems reasonable. I'm not sure whether these are proper ways to fix so I need some help. Any advice would be appreciated. Soap

2 1

Assertion failed on FPU
by Wei Jin 16 Dec '13

16 Dec '13

Hi all, I'm trying to get L4Linux running on my raspberry pi(model B) but there is something wrong that I couldn't figure out. The error message is: Assertion failed: 'Fpu::fpu.current().owner() == current()' [ret=0xf0013544] /home/soap/project/L4/kernel/fiasco/src/kern/arm/thread-arm.cpp:800 at f0012b7c The value of "Fpu::fpu.current().owner()" is 0 which seems to be the value set when fpu initialized. Can anyone help me to fix it? FPU is enabled in Fiasco config and the hello example works. All the components are at latest revision(l4linux:41, fiasco:59, l4re:59) Please let me know if something is missing. Here's the full log: ------------------------------------------- L4 Bootstrapper Build: #37 Sun Dec 15 22:03:04 CST 2013, 4.7.2 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 0fffffff) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 0151b000-0181b000: ramdisk-arm.rd mod08: 01229000-0151a4b8: vmlinuz.arm mod07: 01228000-012280bd: arm-rv.io mod06: 01112000-01227740: io mod05: 01111000-01111173: l4lx.cfg mod04: 010be000-01110bec: ned mod03: 010a4000-010bd498: l4re mod02: 01072000-010a3664: moe mod01: 01068000-010713b0: sigma0 mod00: 01016000-0106787c: fiasco Moving up to 10 modules behind 1100000 moving module 00 { 1016000-106787b } -> { 1905000-195687b } [333948] moving module 01 { 1068000-10713af } -> { 1957000-19603af } [37808] moving module 02 { 1072000-10a3663 } -> { 1961000-1992663 } [202340] moving module 03 { 10a4000-10bd497 } -> { 181b000-1834497 } [103576] moving module 04 { 10be000-1110beb } -> { 1835000-1887beb } [338924] moving module 05 { 1111000-1111172 } -> { 1100000-1100172 } [371] moving module 06 { 1112000-122773f } -> { 1101000-121673f } [1136448] moving module 07 { 1228000-12280bc } -> { 1217000-12170bc } [189] moving module 08 { 1229000-151a4b7 } -> { 1218000-15094b7 } [3085496] moving module 09 { 151b000-181afff } -> { 150a000-1809fff } [3145728] moving module 03 { 181b000-1834497 } -> { 180a000-1823497 } [103576] moving module 04 { 1835000-1887beb } -> { 1824000-1876beb } [338924] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100f000-0x100f15d] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 19ff] { a00} Kern fiasco [ 2000, 5efff] { 5d000} Kern fiasco [ 90000, 968cf] { 68d0} Sigma0 sigma0 [ 98000, 9e17b] { 617c} Sigma0 sigma0 [ 140000, 16d58b] { 2d58c} Root moe [ 170000, 186f0f] { 16f10} Root moe [ 1000000, 10153f7] { 153f8} Boot bootstrap [ 100f000, 100f25a] { 25b} Root Multiboot info [ 1100000, 1876beb] { 776bec} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:01014de4 Roottask config ip:00140260 sp:00000000 Starting kernel fiasco at 000011ec Hello from Startup::stage2 Cache config: ON ID_PFR[01]: 00000111 00000011 ID_[DA]FR0: 00000033 00000000 ID_MMFR[04]: 01130003 10030302 01222100 00000000 FPU0: Arch: VFPv2(1), Part: VFP11(20), r: 5, v: b, i: 41, t: hard, p: dbl/sngl SERIAL ESC: allocated IRQ 57 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: r59 compiled with gcc 4.7.2 for Broadcom 2835 [] Build: #18 Sun Dec 15 21:36:50 CST 2013 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:5f000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;16dfff] [0:16e000;16ffff] [4:170000;186fff] [0:187000;100efff] [4:100f000;100ffff] [0:1010000;10fffff] [4:1100000;1876fff] [0:1877000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 237400 KByte free memory MOE: found RAM from 5f000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [180a000-1823498] [C:503000] l4re BOOTFS: [1824000-1876bec] [C:504000] ned BOOTFS: [1100000-1100173] [C:505000] l4lx.cfg BOOTFS: [1101000-1216740] [C:506000] io BOOTFS: [1217000-12170bd] [C:507000] arm-rv.io BOOTFS: [1218000-15094b8] [C:508000] vmlinuz.arm BOOTFS: [150a000-180a000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0235af1c l4linux | phys=02000000 ephys=0235af1c l4linux | f_sz=002d93b6 memsz=0035af1c flgs=rwx l4linux | PH 1 (t: 4) offs=0029b3f4 vaddr=022933f4 vend=02293418 l4linux | phys=022933f4 ephys=02293418 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x2000298, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa80007a0 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.11.0-l4-svn41 (soap@soap-quantal) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #5 Sun Dec 15 21:56:56 CST 2013 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=2048 init=/bin/sh l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 022b2000 [2760kB] (a bit longer) l4linux | Data: 022b2000 - 022d4100 [136kB] l4linux | Initdata: 02294000 - 022b053c [113kB] l4linux | BSS: 022d93b6 - 0235af1c [518kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:022b3fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3518464 l4linux | section-with-init: Virt: 0x2000000 to 0x235af1b [3435 KiB] l4linux | section-with-init: Phys: 0x0024f000 to 0x005a9f1b, [3435 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x01900000 to 0x058fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3518464 l4linux | text: Virt: 0x2000000 to 0x235af1b [3435 KiB] l4linux | text: Phys: 0x0024f000 to 0x005a9f1b, [3435 KiB] l4linux | l4x_rd_path: rom/ramdisk-arm.rd l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer) (u:b3000a00, v:00000000, sp:022f5fa0) Booting Linux on physical CPU 0x0 Linux version 3.11.0-l4-svn41 (soap@soap-quantal) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #5 Sun Dec 15 21:56:56 CST 2013 CPU: Fiasco [410fb767] revision 7 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Memory policy: ECC disabled, Data cache writeback INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17209 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=2048 init=/bin/sh PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64804K/69636K available (2033K kernel code, 136K rwdata, 604K rodata, 113K init, 518K bss, 4832K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 464.48 BogoMIPS (lpj=2322432) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Setting up static identity map for 0x021e7cb8 - 0x021e7cb8 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations bio: create slab <bio-0> at 0 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 0x00000000, 0xf1199000 // these are values of 'Fpu::fpu.current().owner()' and 'current()' Assertion failed: 'Fpu::fpu.current().owner() == current()' [ret=0xf0013544] /home/soap/project/L4/kernel/fiasco/src/kern/arm/thread-arm.cpp:800 at f0012b7c ------------------------------------------------------- # end of log Thank you for any help! Soap

2 3

Porting libtiff library
by Irvanda Kurniadi 15 Dec '13

15 Dec '13

Hi hackers, I'm trying to port libtiff by following the structure of libjpeg, but I couldn't fix the error in porting libtiff. This is the tree of libjpeg: libjpeg: Control Makefile Lib Lib: build contrib include Makefile build: jconfig.h Makefile contrib: the source file of jpeg-9 library include: Makefile *What is the function of Control file?* libjpeg/Control: provides: libjpeg requires: libc libjpeg/Makefile: PKGDIR = . L4DIR ?= $(PKGDIR)/../.. include $(L4DIR)/mk/subdir.mk *I think this Makefile only for generate the other Makefile in sub-directory. * libjpeg/lib/Makefile: PKGDIR ?= .. L4DIR ?= $(PKGDIR)/../.. TARGET = include build include $(L4DIR)/mk/subdir.mk *This Makefile also only for generating the other Makefile in targeted directories.* libjpeg/lib/include/Makefile: PKGDIR = ../.. L4DIR ?= $(PKGDIR)/../.. CONTRIB_HEADERS = y INCSRC_DIR = $(PKGDIR_ABS)/lib/contrib TARGET = jpeglib.h jmorecfg.h jerror.h \ $(PKGDIR_ABS)/lib/build/jconfig.h include $(L4DIR)/mk/include.mk *What is the function of this Makefile in include directory?* libjpeg/lib/build/Makefile: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libjpeg.a libjpeg.so SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) CONTRIB_INCDIR = libjpeg SRC_C = jaricom.c jcapimin.c jcapistd.c jcarith.c jccoefct.c jccolor.c jcdctmgr.c jchuff.c \ jcinit.c jcmainct.c jcmarker.c jcmaster.c jcomapi.c jcparam.c \ jcprepct.c jcsample.c jctrans.c jdapimin.c jdapistd.c \ jdatadst.c jdatasrc.c jdcoefct.c jdcolor.c jddctmgr.c jdhuff.c \ jdinput.c jdmainct.c jdmarker.c jdmaster.c jdmerge.c \ jdpostct.c jdsample.c jdtrans.c jerror.c jfdctflt.c jfdctfst.c \ jfdctint.c jidctflt.c jidctfst.c jidctint.c jquant1.c \ jquant2.c jutils.c jmemmgr.c jmemnobs.c jdarith.c vpath %.c $(SRC_DIR)/../contrib include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall,$(CFLAGS)) *I think this Makefile is used for compiling all c file in source lib. Is it true that this jconfig.h is obtained by manual configure?* *From this understanding I tried to port libtiff with the same way:* libtiff: Control lib Makefile lib: build contrib include Makefile build: Makefile tiffconf.h contrib: the source file of tiff-4.0.3 include: Makefile libtiff/Control: provides: libtiff requires: zlib libc l4re_c libjpeg libtiff/Makefile: PKGDIR = . L4DIR ?= $(PKGDIR)/../.. include $(L4DIR)/mk/subdir.mk libtiff/lib/Makefile: PKGDIR ?= .. L4DIR ?= $(PKGDIR)/../.. TARGET = include build include $(L4DIR)/mk/subdir.mk libtiff/lib/include/Makefile: PKGDIR = ../.. L4DIR ?= $(PKGDIR)/../.. CONTRIB_HEADERS = y INCSRC_DIR = $(PKGDIR_ABS)/lib/contrib/libtiff TARGET = tif_config.h \ $(PKGDIR_ABS)/lib/build/tiffconf.h include $(L4DIR)/mk/include.mk *I got the tiffconf.h after manual ./configure, then I put the tiffconf.h in build directory.* libtiff/lib/build/Makefile: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libtiff.a libtiff.so REQUIRES_LIBS = libjpeg SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) CONTRIB_INCDIR = libtiff SRC_C = tif_aux.c tif_close.c tif_codec.c tif_color.c \ tif_compress.c tif_dir.c tif_dirinfo.c tif_dirread.c tif_dirwrite.c \ tif_dumpmode.c tif_error.c tif_extension.c tif_fax3.c tif_fax3sm.c \ tif_flush.c tif_getimage.c tif_jbig.c tif_jpeg_12.c tif_jpeg.c \ tif_luv.c tif_lzma.c tif_lzw.c tif_next.c tif_ojpeg.c tif_open.c \ tif_packbits.c tif_pixarlog.c tif_predict.c tif_print.c tif_read.c \ tif_read.c tif_strip.c tif_swab.c tif_thunder.c tif_tile.c tif_unix.c \ tif_version.c tif_warning.c tif_win32.c tif_write.c tif_zip.c vpath %.c $(SRC_DIR)/../contrib/libtiff include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall,$(CFLAGS)) *After I compiled the pkg, then I got this error message:* In file included from ~/l4linux_test/obj/l4/x86/include/contrib/libjpeg/jpeglib.h:27:0, from ~/l4linux_test/src/l4/pkg/libtiff/lib/contrib/libtiff/tif_jpeg.c:88: ~/l4linux_test/obj/l4/x86/include/contrib/libjpeg/jmorecfg.h:263:16: error: expected identifier before numeric constant ... make[8]: *** [tif_jpeg.o] Error 1 please help me to find out this problem, thanks Regards, Irvanda

2 1

Dynamic creation and passing of IPC channels
by Robert Kaiser 13 Dec '13

13 Dec '13

Hi all, I have two tasks running and communicating through an IPC connection (basically the clntsrv demo). Now I would like to extend this a bit: Using an ipc_call(), the client (actually: multiple clients) should be able to register with a server to receive a wakeup IPC at individually different points in time in the future. (First, flawed idea to do this was to *not* use the combined reply_and_wait call on the server side but instead to only do a wait() call and then postpone the corresponding reply() until when the client should be woken up. However, I learned that this will not work because the implicit reply capability will be lost as soon as another ipc call is done by the server.) Next idea now is to create another IPC channel in the client and to pass (via IPC) the send capability for that channel to the server. The client shall than block in an ipc_receive() on that channel and the server can wake it by sending to that channel. I guess this should be possible and for a seasoned Fiasco.OC/L4Re expert it is probably quite easy to do, but I can't seem to find how to: - create an IPC channel at client/server run time (so far, all IPC channels I used were prepared by Ned through lua scripts) - pass the send capability for such a channel to another task via IPC Can anyone point me to some helpful documentation or maybe an example I could cannibalize to implement this (preferably in C, but C++ code would surely be helpful too)? Thanks in advance for any help! Robert

4 6

Re: Request for information on l4 fiasco
by Matthias Lange 10 Dec '13

10 Dec '13

Hi, On 12/10/2013 04:05 PM, Viswa Sekar wrote: > Hello Sir, > thank you for your reply. > > that is really good to hear. > > is there any possibility that i can know the steps for it? > any manuals, or process for it. First, you'll need a proper cross toolchain. One configured for PPC750 should be fine. In the L4Re snapshot archive there is also a README which provides some information on how to build everything. You can adapt the hints given for ARM. Following up the hints Sebastian gave: do you already have a target hardware for your project? Matthias. > > kindly help me. > > thanks in advance > > > On Tue, Dec 10, 2013 at 3:59 PM, Matthias Lange > <mlange(a)sec.t-labs.tu-berlin.de <mailto:mlange@sec.t-labs.tu-berlin.de>> > wrote: > > Hi, > > On Tue, Dec 10, 2013 at 09:51:10AM +0100, Viswa Sekar wrote: > > Hello Sir, > > > > I am on a project on porting l4 fiasco.oc to power pc architecture. > > i am totally new to this. > > kindly provide me documentation/information on the same. > > it will be very useful. > > Fiasco has already been ported to PowerPC. The current state is, that it > compiles but functionality might be broken due to the lack of > testing hardware > on our side. > > Matthias. > > > > > -- > With warm regards, > *VISWA SUBRAMANIAN SEKAR* > Final Year B.E Computer Science and Engineering > PSG COLLEGE OF TECHNOLOGY > Coimbatore. > Phone: +91 94427 94420 > Email: viswasekarsubramanian(a)gmail.com > <mailto:viswasekarsubramanian@gmail.com> > > > -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth

1 0

Request for information on l4 fiasco
by Viswa Sekar 10 Dec '13

10 Dec '13

Hello Sir, I am on a project on porting l4 fiasco.oc to power pc architecture. i am totally new to this. kindly provide me documentation/information on the same. it will be very useful. thanks in advance! : -- With warm regards, *VISWA SUBRAMANIAN SEKAR* Final Year B.E Computer Science and Engineering PSG COLLEGE OF TECHNOLOGY Coimbatore. Phone: +91 94427 94420 Email: viswasekarsubramanian(a)gmail.com

3 2

Microkernel Devroom Accepted Talks and Preliminary Schedule
by Julian Stecklina 06 Dec '13

06 Dec '13

Hello fellow hackers, the microkernel devroom at FOSDEM is packed full with talks! Here is a list of accepted talks and the very preliminary(!) schedule for Feb 2nd. I have changed the requested length of time slots slightly where it made sense. 09:00 - 09:05 Welcoming and Introduction 09:05 - 09:50 Rump Kernels, Just Components Antti Kantee 09:55 - 10:40 Genode as general-purpose OS - Progress report and demonstration Norman Feske 10:45 - 11:30 HelenOS annual update Jakub Jermář 11:35 - 12:05 The microkernel OS Escape Nils Asmussen 13:00 - 13:45 State of the Union: What's new in the L4Re Microkernel System t.b.d. 13:50 - 14:20 Secure applications on top of L4 Sartakov A. Vasily 14:25 - 14:55 GNU/Hurd DDE userland device drivers Samuel Thibault 15:00 - 15:30 Virtualization Dungeon on ARM Stefan Kalkowski 15:40 - 16:25 Read-Copy-Update for HelenOS Martin Děcký 16:30 - 17:00 Rethinking Resource Control Michael Engel I hope those whose talks didn't make it will attend anyway. Julian

1 0

Porting libraries to l4linux
by Irvanda Kurniadi 06 Dec '13

06 Dec '13

Hi hackers, I have read some question about adding libraries to l4/fiasco, but I don't get how to do it exactly. I need to port libtiff and openmpi to compile my program over l4/fiasco. Do you have any documentation about it? I have another question related to running application on top l4linux. Is it possible to run my application on top l4linux; like, if I want to run hello world application over l4linux (not just booting it over l4/fiasco)? I tried to run it by using this configuration: -- Start Hello loader:start( { caps = {}, l4re_bdg = L4.Dbg.Warn, log = {"hello","red"}, }, "rom/hello"); -- Start Linux loader:start( { caps = { log = L4.Env.log:m("rws"), fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=tty0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=linuxrc"); But I think it only run two different applications over l4/fiasco. Do you have any idea how to run the hello application over l4linux? Best regards, Irvanda

2 1

serial_drv failed
by Raja Sekhar 28 Nov '13

28 Nov '13

Hello all, I'm trying to run serial_drv on x86 . But I'm getting the following error...... *serial-drv: virtual base at:0x3000* *L4Re[rm]: mapping for page fault failed with -34 @3030 pc=10008e8* *L4Re: unhandled exception: pc=0x10008e8* What migh be the reason....... *Thanks,* Raja Sekhar

2 1

FOSDEM microkernel devroom submission deadline nears (Dec 1st)
by Julian Stecklina 27 Nov '13

27 Nov '13

Hello fellow microkernel hackers, the deadline for submitting talks to our devroom in Brussels is December 1st. If you haven't already, consider submitting a talk. Details are in the original CfP mail: https://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006068.html Submissions are done via FOSDEM's Pentabarf: https://penta.fosdem.org/submission/ If Pentabarf doesn't work for you, please send your proposal or any other questions regarding the devroom to: microkernel-devroom(a)lists.fosdem.org See you in Brussels, Julian

1 0

[ASK] Make L4 + Fiasco ISO to boot in pandaboard
by Erry Pradana Darajati 25 Nov '13

25 Nov '13

Hello L4hackers, I have a project from my college to build and configure fiasco with l4re to boot and run in Pandaboard. So far i have already build the kernel and l4. But i am having trouble to making ISO for l4re. i follow the instruction using *grub2iso *but it unsuccessful. The Error says : *This mode can only be used with architectures x86 and amd64*. My question is, how can i make ISO for Pandaboard ARM. Thank you for the answer, i am really new for this subject, so i am really appreciate any help -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya*

2 1

Using Trustzone on mx53 and L4Linux
by panton 21 Nov '13

21 Nov '13

Hello Hackers, I am trying to run the example on l4/examples/sys/vm-tz on my imx53 qsb. I get something running but I am pretty sure it is not correct. I have found a message called "Full virtualization with Trustzone" that make me wonder several questions and I hope you can help me. 1- The vm-tz example is supposed to run a L4Linux on NS world. What I don't understand in which format should be the linux-image (or any other app you want to run). I use a gz compress linux image (the same I use for running "L4Linux ARM" example), but I think it should be a bin file (not even a ELF). 2- The vm-tz example make use of l4sigma0_map_iomem() to request a memory mapping, but why not a l4sigma0_map_mem() if what you want is RAM mapping? The serial exit I get is: SIGMA0: Dump of all resource maps RAM:------------------------ [0:70000000;70000fff] [0:70063000;7008ffff] [0:70097000;70097fff] [0:7009f000;7013ffff] [4:70140000;7016cfff] [0:7016d000;7016ffff] [4:70170000;70186fff] [0:70187000;7100cfff] [4:7100d000;7100dfff] [0:7100e000;710fffff] [4:71100000;7182cfff] [0:7182d000;8effffff] IOMEM:---------------------- [0:0;6fffffff] [0:90000000;ffffffff] MOE: Hello world MOE: found 499832 KByte free memory MOE: found RAM from 70000000 to 8f000000 MOE: allocated 496 KByte for the page array @0x7009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [716eb000-71704494] [C:503000] l4re BOOTFS: [71705000-7171e674] [C:504000] vm-tz BOOTFS: [7171f000-7182c73c] [C:505000] io BOOTFS: [71100000-711000bd] [C:506000] arm-rv.io BOOTFS: [71101000-713ea4b4] [C:507000] vmlinuz.arm (My gz compressed linux image) BOOTFS: [713eb000-716eb000] [C:508000] ramdisk-arm.rd MOE: cmdline: moe --init=rom/vm-tz MOE: Starting: rom/vm-tz MOE: loading 'rom/vm-tz' And next is repeated forever without change. VM run VM exit pc:20007000 cpsr:00000013 r0:00000000 r1:0000033b r2:20007100 r3:00000000 r4:00000000 r5:00000000 r6:00000000 r7:00000000 r8:00000000 r9:00000000 r10:00000000 r11:00000000 r12:00000000 lr_svc:00000000 sp_svc:00000000 spsr_svc:00000000 Thanks in advanced for your answers, if any :). Pablo Anton.

2 1

Cons
by Daniel Müller 11 Nov '13

11 Nov '13

Hi, Can someone please explain in a few sentences what the purpose of the cons application (l4/pkg/cons) is? Is it (just) a multiplexer for output? Thanks, Daniel

2 1

question about process generation
by Alexander Aring 08 Nov '13

08 Nov '13

Hi all, I like to implement two processes(if this is the correct word for l4). I want to implement two elf binaries, each of them have a main function. These two processes should communicate over IPC. Is this possible? I have in my modules.list: entry krusty kernel fiasco -serial_esc roottask moe rom/krusty.cfg module foo ... so my init process is 'moe' which should start one than more processes, how can I do that if it possible? In l4 examples of 'ipc' I only saw solution with threads, is this the correct way to initiate new processes? - Alex

2 1

about the snd-base/hot-spot of flexpage mapping
by 冯希顺 08 Nov '13

08 Nov '13

hello everbody. I have a question about the snd-base/hot-spot of flexpage mapping feature. in many l4 documents, there are a lot of words about the snd-base/hot-spot concept, it seem that are a complex mechanism to calculate the send base when the sender's flexpage have different size compares to receiver's flexpage, I have read a lot of documents(l4 user manual/l4 reference manual etc.) about this mechanism, but I can not figure out it... Could you tell why l4 needs this mechanism, and what situation that this mechanism adapt to? And I have another question to Dresden University guys: what is the l4 version of Fiasco.OC based? Thank for your help! Naus

2 1

some question bout L4 memory management
by yakijahn 07 Nov '13

07 Nov '13

Hello L4 hackers Now a days I am studying the memory manage Mechanisms of fiasco kernel and L4RE, and I have some questions: 1) I see that when a process need some memory, a dataspace will be invoked and MOE will retrieve pages from alloc_list as kernel mapping sender, and attach region to region map. if process free a region of memory , the region will be dettached from region map and link the memory back to alloc_list, right? The problem I hold is when and how memory be recycled when a process terminated ? Cause I didn't see system use alloc_list :: free() function when a process had ended, in the process I malloc() about 1 MB memory and didn't free them, but it seems that the memory pre-allocated not been link back to alloc list, could you please tell me when and how will system recycle these memory? If possible, please tell me which code folders is it there. 2) Could you please tell me where are codes(files) that responsible for process virtual memory space management, such as how vitual address be assigned to a variable or pointer. Sometimes i fell to an unhandled page fault when I free pointers, because the page fault address cant be find in region map. Thank you very much for kindly answering Best Reguard YuFen Chang National Tsing-Hua University

2 1

Fiasco.OC API documentation
by Neal H. Walfield 28 Oct '13

28 Oct '13

Hi, I'm looking for documentation on Fiasco.OC's API. I started here: http://os.inf.tu-dresden.de/fiasco/doc.html This led me to this page: http://os.inf.tu-dresden.de/L4Re/doc/ This is mostly a theory page with some links to C++ API documentation, e.g.: http://os.inf.tu-dresden.de/L4Re/doc/group__l4__ipc__api.html Where should I be looking for a formal specification of the Fiasco.OC APIs similar to, say: http://www.cs.cmu.edu/afs/cs/project/mach/public/doc/osf/kernel_interface.ps Thanks for your help! :) Neal

2 2

FOSDEM microkernel devroom video recordings
by Julian Stecklina 18 Oct '13

18 Oct '13

Hello fellow microkernel hackers, the FOSDEM organizers are going to try to provide video recording equipment to all devrooms, but don't have the (wo)manpower to do the actual recording. To have recordings of the talks in the microkernel devroom, we need one volunteer. So if you planned on attending the devroom and are not afraid of a video camera, this is a great opportunity to contribute. Just send me a mail. Of course, every speaker is given a chance to opt out of recording his talk. Thanks, Julian PS. Don't forget to submit your talk until Dec 1st: https://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006068.html

1 0

Invitation to connect on LinkedIn
by Rahul Singhal 17 Oct '13

17 Oct '13

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Rahul Rahul Singhal Student at Indian Institute of Technology, Bombay Mumbai Area, India Confirm that you know Rahul Singhal: https://www.linkedin.com/e/-24ilnx-hmw5i1gw-4n/isd/17375721641/HSxn-9Vu/?hs… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-24ilnx-hmw5i1gw-4n/d2b6lZFP4STrtUgHOnSplZ2KmSz6E… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0

Client Server application with l4linux
by Wajidali Whowe 14 Oct '13

14 Oct '13

Dear all, I am interested in implementing a client-server application between an l4linux instance and an application running on top of u-kernel. I reviewed the client and server examples and thought writing a character driver for an l4linux which serves as either a client or a server. Nevertheless clearly the client / server examples are written in C++. Do you have any suggestion? Best Regards.

2 3

L4/Fiasco.OC & gcc-4.7
by Daniel Müller 14 Oct '13

14 Oct '13

Hello, are there any known issues with Fiasco.OC in conjunction with gcc-4.7? I've just upgrade from 4.6.3 to 4.7.3 and I see warnings of the form: KERNEL: Warning: nothing mapped: (Obj_space) from [0xffffffffffd97dd8/36]: 000000000000044c size: 0000000000000001 to [0xffffffffffd97d28/50] without changes to any of the previously working source codes. Going back to 4.6.3 fixes the issue. Thanks, Daniel

4 5

scanf is not working
by Raja Sekhar 10 Oct '13

10 Oct '13

Hello all, I'm trying to read input using scanf function. but it's not woring. what is the problem and how can i make it work. *Thanks & Regards* Raja Sekhar

2 1

issue while running l4re_fiasco on qemu-system-arm
by Raja Sekhar 10 Oct '13

10 Oct '13

Hello to all, I have cross compiled l4re-fiasco to panda_board and after running the image on Qemu. I'm getting blank screen and i'm not getting any console messages. and this is the command I used is as.. *$ *qemu-system-arm -M beagle -kernel /home/sets/l4re_work/Fiasco.OC-L4Re_arm/build_panda/L4Re/images/bootstrap.elf How to run l4re-fiasco on qemu-system-arm and what are the options i should provide to the command "qemu-system-arm". could please send me a immediate response..... * Thanks & Regards* Raja Sekhar

2 1

FOSDEM 2014 - CfP: Microkernels / Component-based OSes devroom
by Julian Stecklina 09 Oct '13

09 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FOSDEM 2014 - CfP: Microkernels / Component-based OSes devroom Fellow Operating System Hackers, built on the success of the microkernel devroom in the last years, FOSDEM 2014 [1] will host a devroom for developers of open-source microkernel- and component-based operating systems. The devroom is scheduled for Sunday, February 2nd, 2014. We are looking for talks in all areas related to microkernels and component-based operating systems. Possible subjects include, but are not limited to: - introduction of a specific OS or framework, - design of subsystems and general architecture of an OS, - hardware support, - success stories, experiences and lessons learned, - security and robustness, - improving the toolchain, - maintainance and testing, - higher-level languages for OS implementation, - community building. To submit a talk, please create an account at the conference's submission system [2] and select the devroom as the talk's track. Should there be any problems, please send a mail to the devroom mailing list [3]. In your submission, be sure to include: - Title and approximate length of the talk (in the General tab), - the correct track (also in the General tab), - a short abstract (in the Description tab). Talks should not exceed 45 minutes. To help us schedule, please indicate whether your talk is flexible in its length. Please submit your proposals before December 1st. We will announce acceptance and hopefully a rough schedule before Christmas. Of course, there are other ways to contribute and make this event a success, for example by doing a demo of your system. Small devices are no problem, but please check back with us, if you plan to bring larger equipment. Please forward this Call for Participation to anyone interested in participating! See you in Brussels, Julian Stecklina [1] http://fosdem.org/2014 [2] https://penta.fosdem.org/submission/ [3] https://lists.fosdem.org/listinfo/microkernel-devroom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlJVRToACgkQ2EtjUdW3H9k18wCg2Bk9GUuSoB/zoInMyj4Vtmgw 19UAoJQNcTh5funOqyg6ezRz7RY9sEeI =/Kfk -----END PGP SIGNATURE-----

1 0

L4Linux on AMD64 (again)
by Alexander Tarasikov 03 Oct '13

03 Oct '13

Hi, l4-hackers! This message is mainly directed to Adam because most of the work on the latest revisions of l4linux was done by him. I have noticed that AMD64 support is present in most of the arch-l4 code, so I have tried compiling the l4linux kernel in the amd64 mode. I have uncommented the “default y” switch in the KConfig to enable CONFIG_X86_64. Then, I fixed some minor compilation issues: * entry.S did not compile. I had to replace the bitwise or with summation, and replaced the X86_EFLAGS_BIT1 with the integer constant (well, I think I could’ve replaced it with X86_EFLAGS_FIXED) * replaced BIT1 with FIXED in some file, I think, head64.c * added the definition of the early page table count to head64.c (it *is* defined in pgtable-64.h, but I was lazy to figure out why it was not properly included) Then, I applied the amd64 patch to L4Re bootstrap (the one in the mailing list) and raised the modaddr to 0x4000000 to work around region conflicts. I have also launched qemu with 512M memory. First of all, the kernel crashed at the SLAB allocator because the cache pointer was uninitialized. Actually, it nanged in the “arch-l4/kernel/main.c” before calling start_kernel. The reason was that the “head_64.c” contained the code to clean the “early page tables” which wrote to the CR3 register. I have commented the writing to the CR3 and it allowed to move a bit further. Subsequently, I have commented out all the code in the file. SLAB allocator fails to allocate because the function “setup_cpu_cache” in the “mm/slab.c” file has the “init_refok” attribute which means it gets placed into the “ref” section. Selecting SLOB allocator makes it go further. Then, it crashed at the “console_init” call. Console_init calls con_init in “drivers/tty/vt.c”, which freezes at the “pr_info” statement (for some weird reason, it does not jump into the printk() from pr_info). It started working after I lowered the default printk level, so it’s a minor issue. Some more crashes were related to the debug/kmemleak init calls, vfs cache setup which I commented out. Eventually, I had the kernel output the debug via the ttyLv0, not via LOG_printf. It complained about some memory which was not within e820 range. The kernel did not fully boot, because the “init_rest” routine is also marked with “init_refok”. So, I think that only the code from the text section works and the pointers to other sections are invalid. Hope my findings will be useful. Now, I have some questions which could save a few hours of debugging. I would be very grateful if you could answer them: * Is amd64 support planned soon? * Could you explain which part of page table manipulation functions are needed, and which can be commented out? Should the page directory be written somewhere in vCPU instead of CR3? * What load_addr should be used? Zero or 0x100000 (I suspect the former). vG8tQK?z,P-UC`a -- Regards, Alexander

2 1

Re: error in bootstrap when building amd64
by Joel Nider 01 Oct '13

01 Oct '13

Hi, > > ? ==> Linking bootstrap32.elf > > /usr/bin/ld: skipping incompatible > > /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc.a when searching for -lgcc > > /usr/bin/ld: cannot find -lgcc > > collect2: ld returned 1 exit status > > make[4]: *** [bootstrap32.elf] Error 1 > > > Any ideas how to fix it? > > I guess a 32bit version of libgcc might be missing on your system. It is not clear to me why I need a 32-bit bootstrap image when I am trying to build a 64-bit kernel. Is it possible for me to disable/skip this particular file? Everything else seems to build fine. Thanks, Joel

2 1

L4Re::Util::Dataspace_svr
by Daniel Müller 01 Oct '13

01 Oct '13

Hello, L4Re::Util::Dataspace_svr's copy functionality is not very flexible. It only works for local dataspaces which I believe is insufficient. The problem is the "if (!src_cap.id_received())" construct in the L4Re::Dataspace_::Copy case in the dispatch method. Imo this should be something comparable to the validate_ds() method used in region_mapping_svr. Daniel

2 1

ARMV7 virtualization extensions support
by Karoline Haus 01 Oct '13

01 Oct '13

Good afternoon, I'd like to understand if the Fiasco kernel already supports ARM's virtualization extensions (like it supports VT-x and AMD-V), and if not, is that something you are working on? Many thanks for any pointers. Karoline

2 1

error in bootstrap when building amd64
by Joel Nider 01 Oct '13

01 Oct '13

Hi, I'm having trouble building the amd64 L4Re image. I'm building on Ubuntu 12.04 64-bit (kernel 3.2.0-29); make 3.81; gcc 4.6.3 (default) I'm using l4re-core-2013091917 (not the snapshot) that I got from here: http://os.inf.tu-dresden.de/download/snapshots-oc/l4re-core-2013091917.tar.… Everything builds fine until the 'bootstrap' package: === Building package "bootstrap" === make[1]: Entering directory `/home/joel/projects/l4re-core-2013091917/src/l4/pkg/bootstrap' make[2]: Entering directory `/home/joel/projects/l4re-core-2013091917/src/l4/pkg/bootstrap/server' make[3]: Entering directory `/home/joel/projects/l4re-core-2013091917/src/l4/pkg/bootstrap/server/src' make[4]: Entering directory `/home/joel/projects/l4re-core-2013091917/obj/l4/amd64/pkg/bootstrap/server/src/OBJ-amd64_K8' make[5]: Entering directory `/home/joel/projects/l4re-core-2013091917/src/l4/pkg/bootstrap/server/src/ARCH-amd64/libc32' make[6]: Entering directory `/home/joel/projects/l4re-core-2013091917/obj/l4/amd64/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_K8' make[6]: Leaving directory `/home/joel/projects/l4re-core-2013091917/obj/l4/amd64/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_K8' make[5]: Leaving directory `/home/joel/projects/l4re-core-2013091917/src/l4/pkg/bootstrap/server/src/ARCH-amd64/libc32' ==> Linking bootstrap32.elf /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: ld returned 1 exit status make[4]: *** [bootstrap32.elf] Error 1 Any ideas how to fix it? Thanks, Joel

2 1

About the use of C++11 features
by Johannes Schlatow 20 Sep '13

20 Sep '13

Hi, I just noticed that the current snapshot (2013-08-19) doesn't compile with gcc4.4 anymore, which is apparently due to some C++11 incompatibilities (see below). Based on the snapshot from April, I got the Fiasco.OC and L4Re port for the LEON3 (sparc) up and running and would like to merge this with the newest snapshot. Unfortunately, the LEON3 cross compiler (bcc) is based on gcc4.4. So...what's your policy about supporting oldish cross-compilers? And, by the way, how do you feel about including the LEON3 code in your repository? Cheers Johannes Here is the condensed output of a gcc4.4 compilation run: src/kernel/fiasco/src/lib/libk/cxx/function:34: error: ‘cxx::functor<Res(Args ...)>::functor(cxx::functor<Res(Args ...)>&&)’ cannot be defaulted src/kernel/fiasco/src/kern/map_util.cpp: In member function ‘void Mu::Auto_tlb_flush<Mem_space>::global_flush()’: src/kernel/fiasco/src/kern/map_util.cpp:78: error: expected primary-expression before ‘[’ token src/kernel/fiasco/src/kern/map_util.cpp:78: error: expected primary-expression before ‘)’ token src/kernel/fiasco/src/kern/map_util.cpp:741: error: expected primary-expression before ‘[’ token src/kernel/fiasco/src/kern/map_util.cpp:741: error: expected ‘(’ before ‘*’ token src/kernel/fiasco/src/kern/map_util.cpp:741: error: ‘m’ was not declared in this scope src/kernel/fiasco/src/kern/map_util.cpp:741: error: expected ‘(’ before ‘size’

2 1

Booting on Raspberry Pi
by Robert Kaiser 17 Sep '13

17 Sep '13

Hello, i'm currently trying to get Fiasco.OC + L4Re up and running on a Raspberry Pi, but no luck :-( I have gotten as far as building a bootstrap_hello.elf file. According to previous posts here, I should just copy this file to the first partition of a linux-bootable SD card, add an entry like "kernel=bootstrap_hello.elf" to config.txt, and I should see some messages at the serial port as the Pi boots L4. Alas, my Pi stays silent. If I then simply remove the added line from config.txt, leaving everything else the same, Linux boots from the card alright and I can see its messages on the serial port. Thus, I'm confident that my hardware set-up should be OK. I am not absolutely sure wether I got the building of the boot file right. What surprises me is that it is an ELF file: I have previously followed the "Baking Pi" tutorial at http://www.cl.cam.ac.uk/projects/raspberrypi/tutorials/os/. There I used to boot *raw* binaries which expected to be loaded at 0x8000. In contrast, this file here displays as an ELF file with .text starting at 0x01000000. Is that how it should be? The building process also creates a file named "bootstrap_hello", but that is simply a copy of bootstrap_hello.elf. What's the point of this? Thanks a lot for any help Robert Kaiser

2 10

Is mapping database still in use now?
by Sheng-Wei Cheng 15 Sep '13

15 Sep '13

Hi hackers, I've read the paper “µ-kernel Memory Management” and know that, in theory, mapping database is designed for quickly unmaping a page which is recursively mapped to several address spaces. However, is it still in use now in popular implementations like Fiasco.OC? If that is the case, is it used intensively when virtualization on microkernel is involved? (for example, L4Linux etc) Best regards, Lawrence

2 1

vbus problem
by vijay kumar Godavarthy 15 Sep '13

15 Sep '13

Dear all I am using the following code. vbus = l4re_env_get_cap("vbus"); if (l4_is_invalid_cap(vbus)) { printf("Couldn't obtain vbus capability\n"); I am getting the error "Couldn't obtain vbus capability". How to overcome this problem. -- vijay kumar

2 1

How to start DoPe and clients ?
by Rudolf Weber 15 Sep '13

15 Sep '13

Hello, I want to start dope, an fbterminal, and an fb_spectrum, (using l4re-snapshot-2013060718) with the following Start-Script: -- vim:set ft=lua: loader = L4.default_loader; -- Start io vbus_l4linux = loader:new_channel(); local io_buses = { input = loader:new_channel(); fbdrv = loader:new_channel(); }; loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; input = io_buses.input:svr(); fbdrv = io_buses.fbdrv:svr(); l4linux = vbus_l4linux:svr(); }, }, "rom/io rom/x86-legacy.devs rom/l4lx-x86.io"); -- Start fb-drv (but only if we need to) local fb = L4.Env.vesa; if (not fb) then fb = loader:new_channel(); loader:start({ caps = { fb = fb:svr(), vbus = io_buses.fbdrv }, log = { "fbdrv", "r" }, l4re_dbg = L4.Dbg.Warn, }, "rom/fb-drv -m 0x117"); end local gui_caps = { svc = loader:new_channel(), dope = loader:new_channel(), }; -- Start dope loader:start( { caps = { vbus = io_buses.input, fb = fb, svc = gui_caps.svc:svr(), dope = gui_caps.dope:svr(), }, }, "rom/l4dope"); local term_srv = loader:new_channel(); print("Start FBterminal "); e=loader:start( { caps = { fb = gui_caps.svc:create(L4.Proto.Goos, "g=640x480"), term = term_srv:svr(), }, log = { "fbterm", "b" }, l4re_dbg = L4.Dbg.Warn, },"rom/fbterminal"); print("Start fb_spectrum"); e2 = loader:start({ caps = { fb = gui_caps.svc:create(L4.Proto.Goos, "g=320x480"), }, log = { "spectrum", "b" }, l4re_dbg = L4.Dbg.Warn, }, "rom/ex_fb_spectrum_cc"); print("fbterminal exited with: " .. e:wait()); print("ex_fb_spectrum exited with: " .. e2:wait()); -------------------- Result: dope starts, but neither the fbterminal nor the ex_fb_specturm_cc is visible. (The kerneldebugger shows, that the Tasks are not existent ...) What is wrong ? Thank you very much Rudolf P.S: I collect my good experience on http://www.infnet.verein.de/betriebssysteme/kleinkernarch/l4/l4re_conf_2013… with mag it was successfull: http://www.infnet.verein.de/betriebssysteme/kleinkernarch/l4/l4re_conf_2013…

2 1

L4Re::Util::Dataspace_svr
by Daniel Müller 15 Sep '13

15 Sep '13

Hi again, I believe the Dataspace_svr dispatch function is missing a case for L4Re::Dataspace_::Allocate (as declared in l4/pkg/l4re/include/dataspace-sys.h) -- I receive this opcode and since there is no handling the result is a return of -L4_ENOSYS (which will make subsequent processing fail). As a quick fix the attached patch works but there should probably also be a hook (virtual function) in the Dataspace_svr class (and maybe some more sophisticated default processing, not sure). Thanks, Daniel

2 1

Problems with SVN co
by Manuel Dejonghe 10 Sep '13

10 Sep '13

Hi all, I subscribed to this list because last night and now, I have problems checking out the source code: After a 'svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux' I am getting these kind of error messages: ... A l4linux/include/uapi/linux/netfilter/xt_statistic.h svn: In directory 'l4linux/include/uapi/linux/netfilter' svn: Can't open file 'l4linux/include/uapi/linux/netfilter/.svn/tmp/text-base/xt_CONNMARK.h.svn-base': No such file or directory ... A l4linux/include/uapi/linux/netfilter_ipv4/ipt_ttl.h svn: In directory 'l4linux/include/uapi/linux/netfilter_ipv4' svn: Can't open file 'l4linux/include/uapi/linux/netfilter_ipv4/.svn/tmp/text-base/ipt_ecn.h.svn-base': No such file or directory ... A l4linux/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h svn: In directory 'l4linux/include/uapi/linux/netfilter_ipv4' svn: Can't open file 'l4linux/include/uapi/linux/netfilter_ipv4/.svn/tmp/text-base/ipt_ttl.h.svn-base': No such file or directory I have had that as well after only a couple of seconds or after some minutes, with varying milage of completeness, of course. What could be the reason for that ? Does anyone else have strange symptoms currently with the subversion ? thank you very much, lImbus

1 1

L4kproxy::Factory_svr
by Daniel Müller 09 Sep '13

09 Sep '13

Hello, Please find attached a minimal example illustrating a bug in Factory_svr. When executing this example the output is something like: Ned: loading file: 'rom/minimal.lua' Ned: ERROR: ned.lua:199: could not create process: Insufficient memory (: -12) The problem is in parsing the utcb_area parameter in the Factory_hndl::handle_task() method. A patch could be the attached libkproxy.diff which will make the task creation succeed. I would also like to point out that in my opinion there is no point in writing this functionality but never testing or using it (I have been unable to find a single client or test using it). Thanks, Daniel

2 2

Fosdem'14
by Sartakov A. Vasily 09 Sep '13

09 Sep '13

Hello, my dear friends. I am sorry if you receive multiple copies of this message (but I know, most of you will receive copies), but mailing list from uKernel dev room at FOSDEM'13 was destroyed (https://lists.fosdem.org/listinfo). Time rolls on, a FOSDEM'14 is not too far and now it is good time to submit a "uKernel and component based os" dev room. Who would like to organize dev room in this year? I would be proud to make this, but I heard someone from TUD would like to organize Dev room in this year. -- Sartakov A. Vasily sartakov(a)ksyslabs.org

2 2

L4::Cap::move
by Daniel Müller 06 Sep '13

06 Sep '13

Hello, I am wondering is there any particular reason why Cap::move() uses L4_FPAGE_RWX instead of a mask of all bits? l4_task_map(L4_BASE_TASK_CAP, L4_BASE_TASK_CAP, src.fpage(L4_FPAGE_RWX), snd_base(L4_MAP_ITEM_GRANT)); Shouldn't L4_FPAGE_RWX be replaced with L4_CAP_FPAGE_RWSD in order to not restrict rights artificially? I am seeing subtle differences in application behavior in a scenario of mine... Daniel

2 1

Cross-CPU TLB flush problem with Fiasco.OC (r56, r58; exynos5)
by Christian Prochaska 01 Sep '13

01 Sep '13

Hello, I had a situation where CPU 1 accessed the wrong (same as before) physical memory location after it was idle while CPU 0 unmapped the memory page and mapped a different page at the same virtual address afterwards. When a CPU is idle, its TLB gets marked as 'inactive' in the kernel and the CPU doesn't receive cross-CPU TLB flush requests during this time. It seems there is a TLB flush missing somewhere after CPU 1 leaves the idle thread, to compensate for any missed flush requests during the idle time. When I added a 'Mem_unit::tlb_flush()' call after 'enable_tlb(cpu)' in 'Kernel_thread::idle_op()' as a test, this problem did not occur anymore. Christian

2 1

Top runscript
by Daniel Müller 28 Aug '13

28 Aug '13

Hello, I've seen the l4/pkg/top package and find it to be quite interesting. Can someone point me to a lua-runscript to start a program to be monitored by it? What caps do I have to redirect? Thanks, Daniel

1 0

Data transfer mechanisms
by Lluís Vilanova 20 Aug '13

20 Aug '13

Hi, I'd like to compare the performance of two different synchronous data transfer mechanisms: * Copies * Page maps / unmaps For the second one, it looks like I can use the streammap example (pkg/examples/libs/l4re/streammap), although I'm lacking a mechanism to unmap the page before returning control to the client. It would also be nice to be able to pass the server a read-only region. For the first one, I've only found the use of multiple send/recv operations through the limited amount of data available on the message registers. There is a "Gen_string" class in the "ipc_stream" header, which looks like it could support offline string transfers, but it's disabled at compile time and I could not find the actual code in fiasco that handles these transfers. Thanks, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

2 4

Files that Tune Kernel
by Bryan Amato 18 Aug '13

18 Aug '13

Hello everyone, I was wondering what files are the ones that increase the performance of the kernel, besides kernel.hz. Reading in a post by L4, they say that the kernel was not tuned like the Mach Linux port. But I wanted to edit those files to increase performance and to also learn more about what that particular file does. I tried doing this once, but my whole kernel got corrupted from my lack of knowing what is able to be edited and things that had to be there so it could be booted properly. Thanks!

2 1

Desktop Environment
by Bryan Amato 17 Aug '13

17 Aug '13

Hello everyone, I have been using Linux for sometime and only recently tried a special version of BSD, named Dragonfly BSD. What I liked about Dragonfly is that the kernel is not a monolithic kernel. However BSD is not really for me, I prefer the comfort of Linux, so I began searching around the web for a non-monolithic version of the Linux kernel and I came across L4Linux. Looking at the screenshots, I don't see any modern DE's. Does L4L support those desktops like KDE, Gnome and E17? Thanks for all the work you guys are putting into this kernel!

4 3

How to write device driver
by Raja Sekhar 16 Aug '13

16 Aug '13

Hello to all, I want to write a simple character device driver.Can you please give me the procedure for writing device drivers for L4fiasco. * Thanks,* Raja Sekhar

2 1

l4linux with ide-harddisk
by Rudolf Weber 16 Aug '13

16 Aug '13

Hello, I prepared a 32 bit ubuntu system on a virtualbox and replaced the linux - Kernel through the l4re-snapshot-2013060718 - L4Linux-mag-x86 Konfiguration. First I made a disk and add it to the vm and I could mount it ! I wonder ( see later). Now I configured the Ubuntu-Linux-Root-Disk as /dev/hda and: ... piix 0000:00:03.0: IDE controller (0x8086:0x7111 rev 0x01) pci 0000:00:03.0: No interrupt pin configured for device 0000:00:03.0 piix 0000:00:03.0: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd000-0xd007 ide1: BM-DMA at 0xd008-0xd00f hdc: VBOX CD-ROM, ATAPI CD/DVD-ROM drive hdc: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ESC[37mio | ERROR: binding irq 15, result is -1 (Operation not permitted) ESC[0m ESC[33ml4linux | Bind irq to icu failed with -1ESC[0m l4x-irq: Did not get IRQ 15 from IO service ==> I think, the interupt is not delegated from the IO-Server to l4linux My understanding is, that the io-Server manage all interrupts,ioports. But why I could mount a disk ? I dont see a device in x86-legacy.dev, so I add IDE0 and IDE1 (see attachment), and add a systembus disks => new System_bus() { IDE0 => wrap(hw-root.match("ide0")); IDE1 => wrap(hw-root.match("ide1")); } in l4lx-x86.io (see attachment) in the start-config l4lx-gfx.cfg the disks are granted to l4linux (see attachment) As result, the output is piix 0000:00:03.0: IDE controller (0x8086:0x7111 rev 0x01) pci 0000:00:03.0: No interrupt pin configured for device 0000:00:03.0 piix 0000:00:03.0: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd000-0xd007 ide1: BM-DMA at 0xd008-0xd00f hda: VBOX HARDDISK, ATA DISK drive hda: UDMA/33 mode selected hdc: VBOX CD-ROM, ATAPI CD/DVD-ROM drive Switching to clocksource tsc hdc: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ESC[33ml4linux | Bind irq to icu failed with -1ESC[0m l4x-irq: Did not get IRQ 15 from IO service ------------[ cut here ]------------ WARNING: at /home/rw/l4exp/l4re-snapshot-2013060718/src/l4linux/arch/l4/l4lxlib/ l4env/irq_vcpu.c:106 l4lx_irq_dev_startup+0x17a/0x180() Modules linked in: Pid: 1, comm: swapper Not tainted 3.9.0-l4 #1 Call Trace: -> the ERROR "ERROR: binding irq 15, result is -1 (Operation not permitted)" don't appear, but the result is the same. The current output of the serialine is in l4ubuntu.1 The l4-linux I configured with PCI/VPCI see attatchment x86_rw_config like in my last E-mails. Summary: * How to grant the ide-Controllers to l4linux ? * Why l4Linux can't get the interrupt - what is wrong with my configuration ? HW-Question: How are the IDE-Controllers and the PCI related ? Thank you very much Rudolf Weber

2 3

issue in getting vhw_devices....................
by Raja Sekhar 13 Aug '13

13 Aug '13

Hello to all, I've downloaded l4re-core-2013041501.tar.bz2 and extracted and compiled fiasco kernel with following configuration Architecture-> IA-32 processor family, Platform -> PC Platform, CPU -> Intel Pentium Pro After that i compiled L4re env....and I just ran one example ux-vhw(which is the code for display Virtual hardware device). In that I'm getting value *'0'* for the fileld *vhw_offset *from the kernel info structure *struct l4_re_kernel_info_t.* Why It is giving zero and what does it mean....* Thanks*, Raja Sekhar

2 1

Issue in getting Virtual Hardware devices
by Raja Sekhar 10 Aug '13

10 Aug '13

Hello to all, I'm working on L4 fiasco. In that I want to read the virtual hardware devies. for tha I'm running the code from * l4/pkg/example/sys/ux-vhw/main.c *** * 10 #include <l4/sys/ipc.h> 11 #include <l4/sys/vhw.h> 12 #include <l4/util/util.h> 13 #include <l4/util/kip.h> 14 #include <l4/re/env.h> 15 16 #include <stdlib.h> 17 #include <stdio.h> 18 19 static void print_entry(struct l4_vhw_entry *e) 20 { 21 printf("type: %d mem start: %08lx end: %08lx\n" 22 "irq: %d pid %d\n", 23 e->type, e->mem_start, e->mem_size, 24 e->irq_no, e->provider_pid); 25 } 26 27 int main(void) 28 { 29 l4_kernel_info_t *kip = l4re_kip(); 30 struct l4_vhw_descriptor *vhw; 31 int i; 32 33 if (!kip) 34 { 35 36 printf("KIP not available!\n"); 37 return 1; 38 } 39 40 vhw = l4_vhw_get(kip); 41 42 if(vhw) 43 { 44 printf("kip at %p, vhw at %p\n", kip, vhw); 45 printf("magic: %08x, version: %08x, count: %02d\n", 46 vhw->magic, vhw->version, vhw->count); 47 48 for (i = 0; i < vhw->count; i++) 49 print_entry(l4_vhw_get_entry(vhw, i)); 50 } 51 return 0; 52 }** *In the above code at *line no 40* after *calling inline function l4_vhw_get(kip)* I'm getting *vhw=NULL. *and the definition of inline function is from* l4sys/include/vhw.h *is as follows* 80 enum { 81 L4_VHW_MAGIC = 0x56687765, 82 }; 83 84 static inline struct l4_vhw_descriptor * 85 l4_vhw_get(l4_kernel_info_t *kip) L4_NOTHROW 86 { 87 struct l4_vhw_descriptor *v 88 = (struct l4_vhw_descriptor *)(((unsigned long)kip) + kip->vhw_offset); 89 90 if (v->magic == L4_VHW_MAGIC) 91 return v; 92 93 return NULL; 94 } *Here* at line no 90, the v->magic *is having a value of* 0x4BE6344C *which is not equal to* L4_VHW_MAGIC *My qestion is why I'm getting different magic value Instead of 0x56687765, and how can I get correct magic value*. *If there are no virtual hardware device how can i create and integrate into my system........* * * * * *Thanks, Raja Sekhar

2 1

Setting physical CPU for a task
by Lluís Vilanova 06 Aug '13

06 Aug '13

Hi, I've been looking for a way to run some sort of ping-pong example where each task runs on either the same or different CPUs. I've been unable to see if moe's config files allow to start tasks pinned to a specific CPU, and after running the "thread_migrate" example, looks like only one CPU (CPU00) is always used: $ make -C obj/l4/amd64/ qemu E=thread_migrate QEMU_OPTIONS="-serial stdio -vnc ::59000 -smp 2" [...] Not using serial hack in slow timer handler. CPU[0]: AuthenticAMD (6:2:3:0)[00000623] Model: QEMU Virtual CPU version 1.5.1 at 3092MHz 255/512 Entry I TLB (4K pages) 255 Entry I TLB (4M pages) 255/512 Entry D TLB (4K pages) 255 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) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) [...] Ned says: Hi World! Ned: loading file: 'rom/thread_migrate.cfg' migrate | Found 4 CPUs. migrate | Created 12 threads. migrate | Migrated Thread00 -> CPU00 migrate | Migrated Thread01 -> CPU00 migrate | Migrated Thread02 -> CPU00 migrate | Migrated Thread03 -> CPU00 migrate | Migrated Thread04 -> CPU00 migrate | Migrated Thread05 -> CPU00 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU00 migrate | Migrated Thread08 -> CPU00 migrate | Migrated Thread09 -> CPU00 migrate | Migrated Thread10 -> CPU00 migrate | Migrated Thread11 -> CPU00 migrate | Migrated Thread00 -> CPU00 migrate | Migrated Thread01 -> CPU00 migrate | Migrated Thread02 -> CPU00 migrate | Migrated Thread03 -> CPU00 migrate | Migrated Thread04 -> CPU00 migrate | Migrated Thread05 -> CPU00 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU00 migrate | Migrated Thread08 -> CPU00 migrate | Migrated Thread09 -> CPU00 migrate | Migrated Thread10 -> CPU00 migrate | Migrated Thread11 -> CPU00 [... same output forever ...] I've modified "src/l4/conf/modules.list" to add the "thread_migrate" test, and I'm using l4re-snapshot-2013060718, with multiprocessing (with a maximum of 4) enabled on fiasco. Looks like the benchmark always detects (L4::Scheduler::info) the number of maximum CPUs configured in fiasco, but not the number of CPUs provided by QEMU (only CPU 0 is online). Am I missing some step to set all CPUs online? Is it possible to have MOE start tasks pinned to a specific CPU? Thanks a lot, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

2 5

Re: l4-hackers Digest, Vol 124, Issue 4
by Иван Филиппов 06 Aug '13

06 Aug '13

Hi Lluis, Have pretty much the same as you sad - can't load both qemu for unknown memory address, neither for grub2 for Ubuntu 13.04, but it compiles well. I`ll ask what happens tomorrow on upcoming russian Fiasco/Virtualization school with Bjorn Doebel at al. and tell you what happens. Probably the best choose is Qemu emulator, if you don't have already written software, not to reload system every time you need. I compiled with i386 option both FiascoOC/L4RE and them works well. just as here: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/<http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html> 004894.html<http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html> I have 4.7 compiler too. Best wishes, 2013/8/5 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Unable to boot Fiasco.OC on amd64 (Llu?s Vilanova) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 04 Aug 2013 22:44:24 +0300 > From: Llu?s Vilanova <vilanova(a)ac.upc.edu> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Unable to boot Fiasco.OC on amd64 > Message-ID: <87eha95jhj.fsf(a)fimbulvetr.bsc.es> > Content-Type: text/plain; charset="us-ascii" > > Hi there, > > After having to play with the load addresses of both fiasco and some of the > modules [1], I've been able to boot fiasco, but only to find it chokes on > some > assertion, immediately following a pager warning (see error.jpg > screenshot). > > Sorry for using a screenshot, but I've been unable to make the serial > console > work, so no copy&paste is available. > > As I'm new to L4, I don't know if the error is due to my changes or due to > some > other mis-configuration on the boot process. See the attached grub2.txt > for the > GRUB2 entries I've tried (the error corresponds to the first entry). > > I'm using the l4re-core-2013060718 tarball, all compiled on a debian > testing > (gcc 4.7.3). > > Any help on the boot or the serial console support is much appreciated. > > > Thanks a lot, > Lluis > > [1] To avoid some region overlaps, see attached l4.patch, and memory.jpg > for the > memory range configuration of the machine. > >

3 10

mmap2 on L4Linux rev 37
by Sebastian Sumpf 06 Aug '13

06 Aug '13

Hi L4 hackers, recently I started to use L4Linux r37 on ARM and experienced some issues with the 'sys_mmap_pgoff'-system call. When a user-level task tried to map a file the 'pgoff' parameter was usually bogus. Doing a little research I found that it was caused by the 'sys_mmap2' implementation in 'entry.S'. The function overwrites the 'pgoff' argument on the stack with r5 (as it is usually passed from user land), since in L4Linux this code gets called from the dispatch routine, 'pgoff' was set to whatever r5 was, and thus leading to bus errors later on. Cheers, Sebastian -- Sebastian Sumpf Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 1

why Fiasco kernel is named as fiasco
by Raja Sekhar 05 Aug '13

05 Aug '13

Hello to all, I just want to know that why fiasco micro-kernel named as fiasco ..... can you please give me the answer....... * Thanks,* Raja Sekhar

2 1

Unable to boot Fiasco.OC on amd64
by Lluís Vilanova 04 Aug '13

04 Aug '13

Hi there, After having to play with the load addresses of both fiasco and some of the modules [1], I've been able to boot fiasco, but only to find it chokes on some assertion, immediately following a pager warning (see error.jpg screenshot). Sorry for using a screenshot, but I've been unable to make the serial console work, so no copy&paste is available. As I'm new to L4, I don't know if the error is due to my changes or due to some other mis-configuration on the boot process. See the attached grub2.txt for the GRUB2 entries I've tried (the error corresponds to the first entry). I'm using the l4re-core-2013060718 tarball, all compiled on a debian testing (gcc 4.7.3). Any help on the boot or the serial console support is much appreciated. Thanks a lot, Lluis [1] To avoid some region overlaps, see attached l4.patch, and memory.jpg for the memory range configuration of the machine. menuentry "L4" { multiboot /boot/l4/bootstrap -serial module /boot/l4/fiasco /fiasco -serial_esc module /boot/l4/l4f/sigma0 /sigma0 module /boot/l4/l4f/moe /moe module /boot/l4/l4f/hello /hello } menuentry "L4 - L4re" { multiboot /boot/l4/bootstrap -serial module /boot/l4/fiasco /fiasco -serial_esc module /boot/l4/l4f/sigma0 /sigma0 module /boot/l4/l4f/moe /moe --init=rom/hello module /boot/l4/l4f/l4re /l4re module /boot/l4/l4f/hello /hello } -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

1 0

Use of the PC value in interrupt/exception handlers
by Piyus Kedia 03 Aug '13

03 Aug '13

Dear all, We are working on developing a dynamic binary translator for the kernel. Towards this, we wanted to confirm if the interrupted PC value pushed on stack by an interrupt/exception is used by the interrupt/exception handlers? For example, is the PC value compared against a fixed address to determine the handler behaviour (like Linux's page fault handler compares the faulting PC against an exception table, to allow functions like copy_from_user to fault). Basically, we are wondering if it is safe to replace the pushed PC value on stack by another value. This would be safe if the PC value is only used for returning from interrupt, or for reading contents at that PC address (e.g., to decode the instruction at current PC). It would be unsafe if the value of the address itself is meaningful to the handler. We found that in FreeBSD segment-not-present exception handler checks the trapped PC value against some fixed kernel PC by looking at the code, except that it is only used for debugging purposes. It would be nice if somebody could also confirm this. Thanks, Piyus

2 2

l4linux: l4x_setup_memory:Cant get main memory
by Rudolf Weber 01 Aug '13

01 Aug '13

2 13

Fwd: Interrupt Handlers
by Piyus Kedia 01 Aug '13

01 Aug '13

Hi All, I am working on dynamic binary translator. Please tell me if anybody know if in L4-microkernel interrupted kernel PC is ever used in interrupt handlers? Thanks and regards, Piyus

2 1

Using the tmpfs library
by Michael Weiß 01 Aug '13

01 Aug '13

Hi, I want to do some file operations in a native l4re application. using fopen, fgetc, fprintf... from libc. I know that this is possible for the rom filesystem. However, I want to create new files during runtime which are also writable. I found the VFS implementation l4/pkg/tmpfs. but I do not really understand how that VFS stuff works, as there also is no header file for tmpfs. How can I access the tmpfs functionality within my application? For my application it would be sufficient to just have temporary files, which I think is exactly what the tmpfs lib provides. I already linked the tmpfs lib to my application and tried to use mount from sys/mount.h. However, I have no idea which parameters and how the path than has to look like for fopen. Is there some example code which shows howto use this lib in an application? Thanks, Michael

2 1

Unexpected trap while booting Fiasco
by Stefan Fritsch 01 Aug '13

01 Aug '13

Hi, sometimes I get 'Unexpected trap while booting Fiasco' when booting L4Re with grub 0.97. How often this happens seems to depend on the loaded modules, but I haven't been able to determine some rule when it will happen. It does not depend on the number or total size of the modules reaching a certain size. However, since we upgraded to l4re-snapshot-2013060718 from -2013021819, it always happen for me in the below module configuration (it only happened rarely before the upgrade). It looks like parts of fiasco are not mapped at the correct address. Do you have any idea what could cause this? Cheers, Stefan L4 Bootstrapper Build: #1 Mon Jul 29 19:27:21 CEST 2013, x86-32, 4.4.5 Limiting 'RAM' region [ 40005000, c4eb9fff] { 84eb5000} to [ 40005000, bcffffff] { 7cffb000} due to 3024 MB address limit Dropping 'RAM' region [ c50bc000, d82eefff] { 13233000} due to 3024 MB address limit Dropping 'RAM' region [ dafff000, daffffff] { 1000} due to 3024 MB address limit Dropping 'RAM' region [100000000, 11e5fffff] { 1e600000} due to 3024 MB address limit RAM: 0000000000000000 - 000000000009d7ff: 630kB RAM: 0000000000100000 - 000000001fffffff: 523264kB RAM: 0000000020200000 - 0000000040003fff: 522256kB RAM: 0000000040005000 - 00000000bcffffff: 2047980kB Total RAM: 3021MB Moving up to 22 modules behind 1100000 moving module 00 { 319000-3adc23 } -> { a669000-a6fdc23 } [609316] moving module 01 { 3ae000-3f0a71 } -> { a6fe000-a740a71 } [273010] moving module 02 { 3f1000-5be834 } -> { a741000-a90e834 } [1890357] moving module 03 { 5bf000-6ae6e5 } -> { 9882000-99716e5 } [980710] moving module 04 { 6af000-792266 } -> { 9972000-9a55266 } [930407] moving module 05 { 793000-996b94 } -> { 9a56000-9c59b94 } [2112405] moving module 06 { 997000-99802b } -> { 9c5a000-9c5b02b } [4140] moving module 07 { 999000-12e9408 } -> { 9c5c000-a5ac408 } [9765897] moving module 08 { 12ea000-12eab20 } -> { 1100000-1100b20 } [2849] moving module 09 { 12eb000-12eb547 } -> { 1101000-1101547 } [1352] moving module 10 { 12ec000-13da7a1 } -> { 1102000-11f07a1 } [976802] moving module 11 { 13db000-1a39b4e } -> { 11f1000-184fb4e } [6679375] moving module 12 { 1a3a000-7839fff } -> { 1850000-764ffff } [98566144] moving module 13 { 783a000-7c6b5ee } -> { 7650000-7a815ee } [4396527] moving module 14 { 7c6c000-8eebfff } -> { 7a82000-8d01fff } [19398656] moving module 15 { 8eec000-8eec025 } -> { 8d02000-8d02025 } [38] moving module 16 { 8eed000-8ef0f17 } -> { 8d03000-8d06f17 } [16152] moving module 17 { 8ef1000-8f5d42b } -> { 8d07000-8d7342b } [443436] moving module 18 { 8f5e000-942ca58 } -> { 8d74000-9242a58 } [5040729] moving module 19 { 942d000-9610fff } -> { 9243000-9426fff } [1982464] moving module 20 { 9611000-9880749 } -> { 9427000-9696749 } [2553674] moving module 21 { 9881000-988119e } -> { 9697000-969719e } [415] moving module 03 { 9882000-99716e5 } -> { 9698000-97876e5 } [980710] moving module 04 { 9972000-9a55266 } -> { 9788000-986b266 } [930407] moving module 05 { 9a56000-9c59b94 } -> { 986c000-9a6fb94 } [2112405] moving module 06 { 9c5a000-9c5b02b } -> { 9a70000-9a7102b } [4140] moving module 07 { 9c5c000-a5ac408 } -> { 9a72000-a3c2408 } [9765897] Scanning /l4/fiasco -serial_esc -esc -noscreen Scanning /l4/sigma0 Scanning /l4/moe rom/vs-top.cfg Bootloader MMAP: [ 0, 9d800) RAM (1) [ 9d800, a0000) reserved (2) [ e0000, 100000) reserved (2) [ 100000, 20000000) RAM (1) [ 20000000, 20200000) reserved (2) [ 20200000, 40004000) RAM (1) [ 40004000, 40005000) reserved (2) [ 40005000, c4eba000) RAM (1) [ c4eba000, c50bc000) reserved (2) [ c50bc000, d82ef000) RAM (1) [ d82ef000, daeef000) reserved (2) [ daeef000, daf9f000) ACPI NVS (4) [ daf9f000, dafff000) ACPI (3) [ dafff000, db000000) RAM (1) [ db000000, dfa00000) reserved (2) [ f8000000, fc000000) reserved (2) [ fec00000, fec01000) reserved (2) [ fed08000, fed09000) reserved (2) [ fed10000, fed18000) reserved (2) [ fed18000, fed19000) reserved (2) [ fed19000, fed1a000) reserved (2) [ fed1c000, fed20000) reserved (2) [ fee00000, fee01000) reserved (2) [ ffca0000, 100000000) reserved (2) [100000000, 11e600000) RAM (1) Relocated mbi to [0x2e0000-0x2e0304] Loading /l4/fiasco Loading /l4/sigma0 Loading /l4/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /l4/fiasco [ 9d800, 9ffff] { 2800} Arch BIOS [ e0000, fffff] { 20000} Arch BIOS [ 100000, 10a1b3] { a1b4} Sigma0 /l4/sigma0 [ 140000, 18c25f] { 4c260} Root /l4/moe [ 2d0000, 2e4427] { 14428} Boot bootstrap [ 2e0000, 2e0401] { 402} Root Multiboot info [ 300000, 38ffff] { 90000} Kern /l4/fiasco [ 400000, 49dfff] { 9e000} Kern /l4/fiasco [ 1100000, a3c2408] { 92c2409} Root Module [ 20000000, 201fffff] { 200000} Arch BIOS [ 40004000, 40004fff] { 1000} Arch BIOS [ c4eba000, c50bbfff] { 202000} Arch BIOS [ d82ef000, daeeefff] { 2c00000} Arch BIOS [ daeef000, daf9efff] { b0000} Arch BIOS [ daf9f000, daffefff] { 60000} Arch BIOS [ db000000, df9fffff] { 4a00000} Arch BIOS [ f8000000, fbffffff] { 4000000} Arch BIOS [ fec00000, fec00fff] { 1000} Arch BIOS [ fed08000, fed08fff] { 1000} Arch BIOS [ fed10000, fed19fff] { a000} Arch BIOS [ fed1c000, fed1ffff] { 4000} Arch BIOS [ fee00000, fee00fff] { 1000} Arch BIOS [ ffca0000, ffffffff] { 360000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001dc sp:002df150 Roottask config ip:001401c4 sp:00000000 Starting kernel /l4/fiasco at 00300834 EAX f0000000 EBX 2BADB002 ECX 00303000 EDX 00400000 ESI 00035dac EDI 002d81cf EBP 0038fd28 ESP 0038fd20 EIP f00653f0 EFLAGS 00013046 CS 0010 SS 0018 DS 0018 ES 0018 FS 0000 GS 0000 trapno 14, error 00000000, from kernel mode page fault linear address f00653f0 00300055 002dce5c 002dcfe8 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Unexpected trap while booting Fiasco! objdump shows that EIP/pagefault address is the start of init_global_kip(): f00653f0 g F .text 00000014 _ZN3Kip15init_global_kipEPS_ -- genua Gesellschaft fuer Netzwerk- und Unix-Administration mbH Domagkstrasse 7, 85551 Kirchheim bei Muenchen tel +49 89 991950-0, fax -999, www.genua.de Geschaeftsfuehrer: Dr. Magnus Harlander, Dr. Michaela Harlander, Bernhard Schneck. Amtsgericht Muenchen HRB 98238

2 2

Build errors with L4
by Bob Stewart 29 Jul '13

29 Jul '13

I pulled down revisions 56 of l4re per the l4re download instructions on an x86 platform running Ubuntu 13.04. I'm cross compiling for an ARM 8 Beaglebone platform. I created a set of tool links pointing to gcc, g++, ar, ld, etc. from the current Genode toolchain. I then followed the l4 build instructions. The build proceeded normally until is started to link in libc static libraries at which point the following errors killed the build: ... make[5]: Entering directory `/home/bob/fiasco/builds/l4/pkg/loader/server/src/OBJ-arm_armv7a-l4f' ... Compiling main.o ... Compiling slab_alloc.o ... Compiling region.o ... Compiling app_task.o ... Compiling name_space.o ... Compiling log.o ... Compiling global.o ... Compiling sched_proxy.o ... Compiling alloc.o ==> Linking loader /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__exit_handler.o): In function `__new_exitfn': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/_atexit.c:259: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(malloc.o): In function `malloc': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/malloc-standard/malloc.c:1018: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(fwrite.__DO_UNLOCKED.o): In function `fwrite_unlocked': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/fwrite.c:36: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__errno_location.o): In function `__errno_location': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(_trans2w.o):/home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/_trans2w.c:67: more undefined references to `__emutls_v.__libc_errno' follow make[5]: *** [loader] Error 1 Is there some undocumented compiler flag related to TLS I should be setting somewhere to fix these library references? Thanks you Bob Stewart

5 7

Launch of L4Linux
by Maximin Coste 29 Jul '13

29 Jul '13

Hi all, I trying to launch L4Linux over Fiasco.OC+L4RE but here is my serial output: INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing init memory: 112K /bin/sh: can't access tty; job control turned off # io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request. [ ...Launching µC/OS-II part... ] So all I got from L4Linux is "/bin/sh: can't access tty; job control turned off" What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd), is this correct ? This is the content of my modules.list file: modaddr 0x1100000 entry l4LinuxUcos kernel fiasco -serial_esc roottask moe rom/l4lx_ucos.cfg module l4re module ned module io module l4lx_ucos.cfg module vmlinuz.arm module ramdisk-arm.rd module l4ucos module beagle.devs module beagle.io And here is my l4lx configuration file: loader:start( { caps = { log = L4.Env.log:m("rws"), calc_server = calc_server, }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 100*1024*1024):m("rws"), scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x80, 0x70) }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=17000 init=/bin/sh earlyprintk=1"); Thanks in advance, -- Maximin COSTE-LEENHARDT

2 9

Getting fiasco-ux to exit after moe's init process terminates
by John Millikin 27 Jul '13

27 Jul '13

I'm just getting started with L4 and Fiasco, and wanted to try a Hello World. The goal is to have a program which will run in fiasco-ux, print some text to the screen, and then exit back to the terminal. $ cat helloworld.c #include <stdio.h> int main(int argc, char **argv) { printf("Hello world from L4!\n"); return 1; } I'm encountering a problem where after the program runs, moe detects that it's terminated but doesn't itself exit. $ ./fiasco -R './moe --init=rom/helloworld' -l ./l4re -l ./helloworld [...] MOE: cmdline: ./moe --init=rom/helloworld MOE: Starting: rom/helloworld MOE: loading 'rom/helloworld' Hello world from L4! MOE: task 1557475 exited with 1 Looking through src/l4/pkg/moe/server/src, I can't find any obvious way to make moe exit when its init process terminates. Being able to exit seems like fairly important functionality, so I assume it's present somewhere, but I can't figure out how to enable it. moe has no flags related to exiting, and its main() appears to end in the infinite-loop server.loop_noexc() procedure. Is exiting supported? If yes, how do I enable it? If no, why, and would patches be accepted to do this?

2 1

Problem with setting up namespaces
by Johannes Schlatow 19 Jul '13

19 Jul '13

Hi, I was just trying to set up a simple application that uses L4Re namespaces. I therefore took the clntsrv example and modified it as shown in the diff below with the result that the server blocks on the bind_thread() call. Am I missing something? Cheers Johannes diff --git a/src/l4/pkg/examples/clntsrv/clntsrv.cfg b/src/l4/pkg/examples/clntsrv/clntsrv.cfg index bb2ae50..dd7dfa5 100644 --- a/src/l4/pkg/examples/clntsrv/clntsrv.cfg +++ b/src/l4/pkg/examples/clntsrv/clntsrv.cfg @@ -9,13 +9,16 @@ local ld = L4.default_loader; -- Channel for the two programs to talk to each other. local calc_server = ld:new_channel(); +local server_ns = ld:create_namespace({ calc_server = calc_server:svr()}); +local client_ns = ld:create_namespace({ calc_server = calc_server}); + -- The server program, getting the channel in server mode. -ld:start({ caps = { calc_server = calc_server:svr() }, +ld:start({ caps = { namespace = server_ns }, log = { "server", "blue" } }, "rom/ex_clntsrv-server"); -- The client program, getting the 'calc_server' channel to be able to talk -- to the server. The client will be started with a green log output. -ld:start({ caps = { calc_server = calc_server }, +ld:start({ caps = { namespace = client_ns }, log = { "client", "green" } }, "rom/ex_clntsrv-client"); diff --git a/src/l4/pkg/examples/clntsrv/server.cc b/src/l4/pkg/examples/clntsrv/server.cc index 2f2e3fc..9c4c0b9 100644 --- a/src/l4/pkg/examples/clntsrv/server.cc +++ b/src/l4/pkg/examples/clntsrv/server.cc @@ -12,6 +12,7 @@ #include <l4/re/util/cap_alloc> #include <l4/re/util/object_registry> #include <l4/cxx/ipc_server> +#include <l4/re/namespace> #include "shared.h" @@ -60,12 +61,34 @@ main() { static Calculation_server calc; - // Register calculation server - if (!server.registry()->register_obj(&calc, "calc_server").is_valid()) - { - printf("Could not register my service, is there a 'calc_server' in the caps table?\n"); - return 1; - } + L4::Cap<L4Re::Namespace> ns = L4Re::Env::env()->get_cap<L4Re::Namespace>("namespace"); + if (!ns.is_valid()) { + printf("Could not get namespace cap from cap table.\n"); + return 1; + } + L4::Cap<L4::Ipc_gate> calc_server = L4Re::Util::cap_alloc.alloc<L4::Ipc_gate>(); + + if (ns->query("calc_server", calc_server) != 0) { + printf("Could not get 'calc_server' cap from namespace\n"); + return 1; + } + + if (!calc_server.is_valid()) { + printf("calc_server cap is invalid\n"); + return 1; + } + + l4_umword_t id = l4_umword_t(0xcaffee); + L4::Cap<L4::Thread> tcap = L4Re::Env::env()->main_thread(); + + printf("bind_thread()...\n"); + int err = l4_error(calc_server->bind_thread(tcap, id)); + if (err < 0) { + printf("failed\n"); + return 1; + } + + printf("OK\n"); printf("Welcome to the calculation server!\n" "I can do substractions and negations.\n");

4 6

Fiasco.OC Kernel memory running out (I think)
by Daniel Waddington 18 Jul '13

18 Jul '13

Hi, I'm using Fiasco.OC r56 on x86_64 (with Genode). After doing quite a lot of memory mapping, mem_map finally fails. It seems that the _allocators[0]->alloc(...) fails during the Mapping_tree::new operator creation of a Mapping_tree object in the Treemap::tree method. How can I increase the available kernel memory attached to this allocator? Thanks Daniel

2 1

Error during the "ned" package build (svn revision 42)
by ggasnier31＠free.fr 16 Jul '13

16 Jul '13

Hello, I got the following error building the "ned" package for ARM architecture (Cortex-A9, Pandaboard). I use the last Linaro toolchain "gcc-linaro-arm-linux-gnueabihf-4.7-2012.12-20121214_linux". === Building package "ned" === make[1]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make[2]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' ... Building /home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/.general.d make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' ... Building .general.d ... Building Makefile.inc make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: *** No rule to make target `ned.lua.bin.o', needed by `ned'. Stop. make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Commenting the line "OBJS += ned.lua.bin.o" in the file l4/pkg/ned/server/src/Makefile gives this error. ==> Linking ned lua.o: In function `lua(int, char const* const*)': /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_start' /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_end' make[4]: *** [ned] Error 1 make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Regards, Guillaume GASNIER

3 3

x86_fb-example
by Rudolf Weber 15 Jul '13

15 Jul '13

Hello, I want to try out the x86-fb-example in the l4re-snapshot-2013060718. I found the following patch necessary: --- src/l4/conf/examples/x86-fb.list.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.list 2013-07-12 18:23:39.688816451 +0200 @@ -1,5 +1,5 @@ -modaddr 0x1100000 +modaddr 0x2000000 entry x86-fb-example bootstrap bootstrap -serial @@ -13,4 +13,4 @@ module ned module fb-drv module mag -module ex_fb_spectrum +module ex_fb_spectrum_cc --- src/l4/conf/examples/x86-fb.cfg.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.cfg 2013-07-12 18:12:30.837274646 +0200 @@ -64,5 +64,5 @@ l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8), }, - "rom/ex_fb_spectrum"); + "rom/ex_fb_spectrum_cc"); print("ex_fb_spectrum exited with: " .. e:wait()); I generated a iso-Image with make grub2iso E=x86-fb-example MODULES_LIST=/home/rw/l4exp/l4re-snapshot-2013060718/src/l4/conf/examples/x86-fb.list and started with qemu-system-i386 -cdrom images/x86-fb-example.iso -serial stdio It's great to have examples ! Greetings Rudolf Weber http://www.infnet.verein.de/home/rw/index.html Computer Science and Network Club Ravensburg

2 1

Help needed
by vijay kumar godavarthy 06 Jul '13

06 Jul '13

Dear all, I am a newbie to l4re and fiasco. I would like to execute the client-server example given in the example directory. Please let me know the steps to be followed. In case I write a new server how to compile and execute it in QEMU. Best regards and many thanks -- vijay kumar

2 1

A interprocess communication system for two l4linux instances
by Wajidali Whowe 05 Jul '13

05 Jul '13

Dear all, I am trying to implement an IPC method between two l4linux instances (lets call them as vmlinuz1 and vmlinuz2) using l4ser driver. Nevertheless both l4linux instances stuck during boot up printing, the following last sentence: "vmlinuz.| L4 serial driver" Going over the driver/tty/serial/l4ser.c file, I have seen that the stuck position line is in the function "l4ser_init_port"; "t = L4XV_FN(l4_msgtag_t, l4_icu_bind(l4ser_port[num].vcon_cap, 0, l4ser_port[num].vcon_irq_cap));" The following is my lua script: local ttyChannel = l:new_channel(); local hid = l:new_channel(); local linux_caps = { log = L4.Env.log:m("rws"); vbus = io_caps.linux_bus, rtc = rtc_caps.rtc, ev = hid:svr(), rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps, }, "rom/vmlinuz1 mem=512M l4ser.add=ttyMv0 l4-input-srv.enable=1 console=ttyLv0 ramdisk=rom/myRamdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/myRamdisk init=/sbin/init"); local linux_caps2 = { vbus = io_caps.linux_bus2, rtc = rtc_caps.rtc, rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps2, }, "rom/vmlinuz.android mem=512M l4ser.add=ttyMv0 console=ttyLv0 ramdisk=rom/ramdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/ramdisk init=/sbin/init"); How do you think that might cause the problem? Best regards and many thanks.

1 0

Thought you'd find this interesting
by Rahul Singhal 30 Jun '13

30 Jun '13

Hi! I’ve just learned about the water crisis and thought you would be interested to check out this story: https://waterforward.charitywater.org/et/xclFZthf Let me know what you think! Thanks, Rahul -- Sent via WaterForward, an initiative of charity: water WaterForward, 387 Tehama Street, San Francisco, CA 94103, USA. Click here to unsubscribe: https://waterforward.charitywater.org/opt_out?et=xclFZthf

1 0

15th Real Time Linux Workshop - Call for Papers
by Nicholas Mc Guire 25 Jun '13

25 Jun '13

15th Real Time Linux Workshop 1st Call for Papers October 28 - 31, 2013 Dipartimento tecnologie innovative Scuola universitaria professionale della Svizzera italiana Lugano-Manno Switzerland Following the meetings of academics, developers and users of real-time and embedded Linux at the previous 14 Real Time Linux Workshops held world-wide (Vienna, Orlando, Milano, Boston, Valencia, Singapore, Lille, Lanzhou, Linz, Guadalajara, Dresden, Nairobi, Prague and Chapel Hill) - the 2013 Real Time Linux Workshop will come to the Scuola Universitaria Professionale della Svizzera Italiana in Lugano-Manno, Switzerland. It will be held from October 28 to October 31, 2013. Rationale Real-time systems have evolved over the past decades in a relatively calm manner - performance has increased, one can say dramatically, but the main paradigms were pretty stable since the mid 80s. With the considerable increase of computing power, notably with multicore systems becoming mainstream in embedded devices, the requirements on RTOS are shifting and the tools are again trying to catch up. In stark contrast to 1999 (when the first RTLWS took place), Linux has a strong position in all kind of embedded systems, ranging from consumer electronics to network devices and a broad range of industrial applications including safety related systems. The technological resources suitable for high-availability, real-time, and safety critical systems have been continuously expanding and improving - allowing to cover the entire development life cycle of industrial projects based on open-source tools. At the core of this development is the availability of stable operating systems with reliable real-time properties. Extending and improving the real-time properties of Open Source RTOS is a continuous research and development effort. The OSADL has set itself the ambitious goal to document these efforts and it's most effective tool to do so is the annual Real Time Linux Workshop. Call for papers Authors from regulatory bodies, academics, industry as well as the user-community are invited to submit original work dealing with general topics related to Open Source and Free Software based real-time systems research, experiments and case studies, as well as issues of integration of open-source real-time and embedded OS. A special focus will be on industrial case studies and safety related systems. Topics of interest include, but are not limited to: - Modifications and variants of the GNU/Linux operating system and extending its real-time capabilities, - Contributions to real-time Linux variants, drivers and extensions, - Tools for the verification and validation of real-time properties, - User-mode real-time concepts, implementation and experience, - Real-time Linux applications, in academia, research and industry, - Safety related FLOSS systems, - Safety related systems using FLOSS components, - FLOSS Tools used to analyze, verify or validate safety properties, - Work in progress reports, covering recent developments, - Educational material on real-time Linux, - RTOS core concepts, RT-safe synchronization mechanisms, - RT-safe IPC mechanisms for RT and non RT components, - Analysis and benchmarking methods and results of real-time GNU/Linux variants, - Debugging techniques and tools, both for code and temporal debugging of core RTOS components, drivers and real-time applications, - Real-time related extensions to development environments Abstract submission If you wish to present a paper at the workshop, please submit an abstract using the submission page at https://www.osadl.org/RTLWS15-Abstract.submission-form.0.html. Final paper to be included into the RTLWS15 Proceedings Upon acceptance of an abstract by the RTLWS15 Program Committee, the author will be invited to submit a full paper in a form defined by https://www.osadl.org/paper.tgz. A detailed description of the editing and formatting process will be provided along with the notification email. Further information: http://www.osadl.org/RTLWS Important dates July 29, 2013 - Abstract submission deadline August 26, 2013 - Notification of acceptance September 23, 2013 - Submission of final paper October 28-31, 2013 - Workshop Organization committee: Local organizers: - Roberto Bucher, Scuola universitaria professionale della Svizzera italiana SUPSI, Switzerland OSADL/RTLF - Carsten Emde, OSADL - Nicholas Mc Guire, OSADL - Andreas Platschek, ICT, Vienna University of Technology, Austria Program committee: - Alexey Khoroshilov, ISPRAS, Russia - Andrea Bastoni, SYSGO AG, Germany - Andreas Platschek, TU-Wien, Austria - Bernhard N�lte, IQSE TueV SueD Rail, Germany - Carsten Emde, OSADL, Germany - Cheng Sheng, Beijing Shenzhou Aerospace Software Technology, China - Fans, Spectrum Sys, China - Georg Schiesser, OpenTech EDV Research, Austria - Herman H�rtig, Technische Universit�t Dresden, Germany - Julia Lawall, Inria/LIP6, France - Julien Delange, Carnegie Mellon Software Engineering Institute, USA - Klaus Reichl, Base Systems Technology Thales, Austria - Matthias Auchmann, A&R TECH, Austria - Michal Sojka, Czech Technical University in Prague, Czech Republic - Nicholas Mc Guire, OpenTech EDV Research, Austria - Paul E. McKenney, IBM Linux Technology Center, USA - Paolo Mantegazza, Politecnico di Milano, Italy - Peter Okech, University of Nairobi, Kenya - Peter Wurmsdobler, Aveillant Ltd, UK - Peter Zijlstra, RedHat, Netherlands - Philippe Gerum, Xenomai, France - Roberto Bucher, SUPSI, Switzerland - Shawn Choo, Weslab, Singapur - Stefan Schoenegger, B&R, Austria - Steven Rostedt, RedHat, USA - Thomas Gleixner, Linutronix, Germany - Yutaka Matsuno, University of Electro-Communications, Japan - Zhou Qingguo, DSLab, Lanzhou University, China Workshop organizers: - Dipartimento Tecnologie Innovative, SUPSI, Switzerland - Open Source Automation Development Lab (OSADL) Roberto Bucher Carsten Emde Nicholas Mc Guire Andreas Platschek

1 0

How to run simple client server example
by Thang Tran 24 Jun '13

24 Jun '13

Hi, I'm new to Fiasco and L4Re. I want to write a new program in C++ which will run on L4Re. I'm looking at the simple client server example in the l4/pkg/examples/clntsrv directory for my reference. I was able to get it compiled eventually on L4Re, but I have no idea how to run it. Is there anyway that I can run examples/clntsrv package just like we run the hello package by using grub2iso and qemu? Thanks in advance, Thang Tran.

2 1

Unable to boot 64bit hello
by Daniel Müller 14 Jun '13

14 Jun '13

Hi, I tried booting a 64bit hello world program on L4/Fiasco but that fails with a region overlap: ============================================= xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019dd88 TOTAL: 0000000000000000->000000007f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 Daemon running with PID 9320 net0: 00:16:3e:72:79:e5 using rtl8139 on PCI00:04.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] DHCP (net0 00:16:3e:72:79:e5)... ok net0: 192.168.178.200/255.255.255.0 gw 192.168.178.54 Booting from PXE menu boot PXEBS (net0 type 128).... ok Next server: 192.168.178.54 Filename: pxeboot.0 tftp://192.168.178.54/pxeboot.0... ok L4 Bootstrapper Build: #7 Sun Jun 9 16:51:46 CEST 2013, x86-64, 4.6.3 RAM: 0000000000000000 - 000000000009a7ff: 618kB RAM: 0000000000100000 - 000000007f7b9fff: 2087656kB Total RAM: 2039MB New region for list regions: [ 20d000, 4c62c9] { 2b92ca} Root Module overlaps with: [ 2d0080, 2e45c7] { 14548} Boot bootstrap Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ e0000, fffff] { 20000} Arch BIOS [ 106000, 1a646f] { a0470} Root Module [ 1a7000, 20c9bd] { 659be} Root Module [ 2d0080, 2e45c7] { 14548} Boot bootstrap [ 1013000, 10a8fff] { 96000} Boot bootstrap-ptab64 [ fc000000, ffffffff] { 4000000} Arch BIOS region overlap Key press reboots... ============================================= Everything works for 32bit. I took a look at bootstrap/server/src/startup.cc. I verified that modaddr is correctly passed to boostrap in both cases (32 and 64bit; it is 0x2000000 everytime). It appears that the failure happens in the call to add_boot_modules_region(): /* we're just a GRUB-booted kernel! */ add_boot_modules_region(mbi); if (_mod_addr) move_modules(mbi, _mod_addr); I do not fully understand all this code but to me this looks like a logic error: first the move should happen to honor "-modaddr" and only then the overlap check should be done. Here is the output for 32bit: ============================================= L4 Bootstrapper Build: #3 Sun Jun 9 16:55:38 CEST 2013, x86-32, 4.6.3 RAM: 0000000000000000 - 000000000009a7ff: 618kB RAM: 0000000000100000 - 000000007f7b9fff: 2087656kB Total RAM: 2039MB Moving up to 7 modules behind 2000000 moving module 00 { 139000-1ba783 } -> { 2829000-28aa783 } [530308] moving module 01 { 1bb000-21015e } -> { 28ab000-290015e } [348511] moving module 02 { 2e5000-51f51c } -> { 2901000-2b3b51c } [2336029] moving module 03 { 520000-762e3b } -> { 2000000-2242e3b } [2371132] moving module 04 { 763000-8880c6 } -> { 2243000-23680c6 } [1200327] moving module 05 { 211000-211080 } -> { 2369000-2369080 } [129] moving module 06 { 889000-9616a6 } -> { 236a000-24426a6 } [886439] Scanning /fiasco -serial -serial_esc -comspeed 115200 -comport 1 -nokdb Scanning /sigma0 Scanning /moe rom/hello.lua Bootloader MMAP: [ 0, 9a800) RAM (1) [ e0000, 100000) reserved (2) [ 100000, 7f7ba000) RAM (1) [ fc000000, 100000000) reserved (2) Relocated mbi to [0x2e0000-0x2e043f] Loading /fiasco Loading /sigma0 Loading /moe find kernel info page... found kernel info page at 0x400000 ... ============================================= Since the module addresses are also different between the two version this might also be an issue with the linker scripts (and thus just luck that the 32bit version boots), I would guess. I am using a Xen VM for testing. Any help would be appreciated. Thanks, Daniel

3 6

How to make task run on different cores?
by Chao-Jui Chang 12 Jun '13

12 Jun '13

Hi, I start up 4 L4Linux on intel core2quad platform. In jdb, I can see 4 vmlinuz on the task list (command 's' in jdb). Next, I run 4 benchmarks, one in each L4Linux, but the experiment result shows that the 4 benchmark are running on the same core. The kernel seems not scheduling them to different cpu cores. I have enabled "Enable multi processor support" option in fiasco config menu and the jdb shows there are 4 cores: *** Cut start *** ----------------------------------------------------------------------- CPU 0 [f000d2a0]: IRQ ENTRY CPU 1 [f0022451]: Maskable Interrupt CPU 2 [f0022451]: Maskable Interrupt CPU 3 [f0022451]: Maskable Interrupt jdb: g *** Cut end *** But the running benchmarks are not showing on the task list(command 's' in jdb), is it normal? I remember in ARM L4Linux, the task list will show 'vmlinuz', 'sh', 'benchmark', ...,etc. Best Regards, Chao-Jui

2 5

How Fiasco reclaim task resources when the task exits (abnormally) ?
by BogDan 11 Jun '13

11 Jun '13

Hello, What happens with a task resources when a task crashes or it leaks resources at exit? How this resources (e.g. memory, file descriptors, any other capabilities) are reclaimed back by the o.s. ? Cheers, BogDan.

2 3

Re: Fiasco.OC with ARM TrustZone
by Chao-Jui Chang 11 Jun '13

11 Jun '13

Hi Adam, Thanks for your reply. After I change the memory to 1023, it runs but stops at ### Timer for CPU0 is at IRQ 28 Calibrating timer loop... ### By the way, how to turn on the module loading information during booting? The latest snapshot and svn only prints message starting from "Hello from Startup::stage2" ### Start cur ### Exynos4412 # run fiasco Partition1: Start Address(0x1000), Size(0x32000) reading bootstrap.raw 803080 bytes read Boot with zImage Starting kernel ... Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 305 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned director compiled with gcc 4.5.2 for Samsung Exynos [] Build: #22 17:15:49 CST 2013 Timer for CPU0 is at IRQ 28 Calibrating timer loop... ### End ### Thanks, Chao-Jui 2013/5/12 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Hi, > > On Tue May 07, 2013 at 17:51:42 +0800, Chao-Jui Chang wrote: > > Is trustzone working on exynos 4412 platform? > > It is generally supposed to work but this also depends on the particular > board/system due to board configs etc. > > > I have selected the follow item in Fiasco config menu: > > * Platform Timer (Multi-core timer) > > * Use ExtGic > > * Execution Model (TrustZone normal side) > > > > But it stop at early stage. > > Same result for Execution Model (Standard mode). > > but no message for Execution Model (TrustZone secure side). > > One reason could be the configured amount of memory, is it 1023 or 1024MB? > > > If the trustzone is disabled in u-boot, the 'Standard mode' works fine. > > That could also indicate that. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >

2 5

Program development for L4Re
by Rahul Singhal 11 Jun '13

11 Jun '13

I have recently ported l4 fiasco + l4Re on raspberry pi. I tested the port with the sample hello world program and it works fine.Now I want to write some of my own programs (C++, C and python) and run it on this environment. All I have done as of now is modify the sample hello world code a bit and test it. How do I go about doing this and where to start from? i appreciate your help. Regards Rahul

2 1

Task threads are not killed at exit
by BogDan 10 Jun '13

10 Jun '13

Hello, Not all the task threads are killed when a task exits or it crashes. I've created a simple example here: http://paste.kde.org/760274 After application crashes (line 22), test thread is still alive, I still can see "Test thread alive" message printed. If I call exit or return instead to crash the task, the test thread is still alive . Cheers, BogDan.

2 3

Re: <http://l4ka.org/> down?
by Thomas Schwinge 08 Jun '13

08 Jun '13

Hi! As the l4ka mailing list also seems to be defunct (though, my email didn't bounce), forwarding the question to the Dresden L4 folks as well as the registrant of the l4ka.org domain: On Thu, 06 Jun 2013 10:06:02 +0200, Thomas Schwinge <thomas(a)codesourcery.com> wrote: > On Wed, 05 Jun 2013 17:10:11 +0200, I wrote: > > On Wed, 5 Jun 2013 17:02:03 +0300, Fotis Koutoulakis <fotis.koutoulakis(a)gmail.com> wrote: > > > On http://www.gnu.org/software/hurd/microkernel.html the link for the > > > paper "On Microkernel Construction" appears to be dead. This patch > > > replaces the dead link with a working one. > > > > > [ mkernelconstructionurl.patch: application/octet-stream (as text/x-diff) ] > > > 14c14 > > > < [[Liedtke]] explains in [On Microkernel Construction](http://l4ka.org/publications/paper.php?docid=642) > > > [...] > > > As it appears that <http://l4ka.org/> generally is down (»Unconfigured > > server«) Now the server completely disappeared. > > at the moment. I suggest we wait a few days and see whether it > > comes back. If not (huh...), I'd like to use a more canonical [...] > > Any comments from the l4ka list? Is this a permanent outage, or just > temporary? Grüße, Thomas

1 0

arm-linux-ld not found while compiling l4-fiasco microkernel
by Rahul Singhal 06 Jun '13

06 Jun '13

I am trying to port L4-fiasco + L4Re to raspberry pi. But when I compile fiasco, it throws an error saying arm-linux-ld not found. I found that I will need cross compiler binaries to compile the fiasco microkernel. But where to find them. Please help! Thanks in advance.

3 2

Hello scenario gets stuck
by Markus Partheymueller 06 Jun '13

06 Jun '13

Hey, I'm having trouble booting the hello example on real hardware. The following config is booted via PXE: addr 0x2000000 exec mparthey/foc/bootstrap -serial load mparthey/foc/fiasco -serial -serial_esc -esc load mparthey/foc/sigma0 load mparthey/foc/moe load mparthey/foc/l4re load mparthey/foc/hello But it hangs after "MOE: Hello world". I can still enter the Kernel debugger, listing these task and thread objects: [Objects] 1 f007e020 [Task ] {KERNEL} R=2 6 ffdc6134 [Thread ] {KERNEL} C=0 R=1 current 7 fffe8f70 [Task ] {sigma0 } R=3 8 ffd80134 [Thread ] {sigma0 } C=0 S=D:7 R=3 9 fffe8f18 [Task ] R=3 a ffd83134 [Thread ] C=0 S=D:9 R=4 Backtrace on thread a yields an address 0x143d7d in moe (?), belonging to void List_alloc::merge() { List_alloc_sanity_guard __attribute__((unused)) guard(this, __func__); Mem_block *c = _first; while (c && c->next) 143d7d: 8b 00 mov (%eax),%eax 143d7f: 85 c0 test %eax,%eax 143d81: 75 ee jne 143d71 <_ZN22Single_page_alloc_base5_freeEPvmb+0x51> _ZN22Single_page_alloc_base5_freeEPvmb(): [...]/src/l4/pkg/moe/server/src/page_alloc.cc:109 } On a different machine the exact same setup works fine. Has anyone got a clue what goes wrong here? If I should get more information out of the kernel debugger, just let me know. Cheers Markus

2 5

Re: How to catch unhandled exceptions ?
by Björn Döbel 04 Jun '13

04 Jun '13

Hi, [..] > So far so good! This is exactly what I want to do, to have a way to be notified > by the kernel about any exception of a thread. Now my problem is that I > get no notification when something bad happens (e.g. division by 0 or a > page fault), is there any example where I can look to see how to use > thread control + exc_handler and co ? I don't think I really know what to > pass to exc_handler method, I tried to pass a L4::Server_Object::obj_cap() > object but nothing happened ... The page fault handler and the exception handler are Fiasco.OC threads. Hence, you pass thread capabilities to those calls. Page faults go to the PF handler , all other exceptions end up in the exception handler thread. In the thread you would then do something like while (1) { msg = l4_ipc_receive(); inject_exception(); } In inject_exception() you can use the Thread::ex_regs system call, which allows you to modify the IP/SP of a thread. [..] >> Also, C++ exceptions need to be caught in the thread that raised the >> exception, otherwise the exceptions causes a call to std::terminate, >> wich will abort your application. Hence, you'd need try/catch statements >> for all potential hardware exceptions around all your threads' code. >> > > Of course you need to add try/catch statements :) The beauty is that if > you'll do it, you'll have a chance to survive to save your data, if not, > then, as you said, std::terminate will be called and you get the same > effect. There may be libraries (e.g., libc_be_signal) that spawn their own threads and where you do not have control over potential try/catch statements in their code. But that might not be an issue for you. >> I'm not saying it can't be done (I vaguely remember Choices OS [1] doing >> this), it's just not what we are doing on Fiasco right now. >> > > AH, sorry , I think is a misunderstanding here, I don't want you to do it in > Fiasco (even I think it will be very nice feature), I want to be able to do it > in my apps (at user-level not kernel level)! Sure, that's what I meant as well. Cheers, Bjoern

2 2

target CPU does not support ARM mode
by Maximin Coste 04 Jun '13

04 Jun '13

I have a new error, appears from nowhere... I dowloaded the last L4RE version from the website, edited the mk/Makeconf file to put my "arm-none-aebi-" compilator and when i type: $ make O=build config/ I select ARM 7A / BeagleBoard, as usual, as it always worked... Here is my output: [...] <stdin>:1:0: error: target CPU does not support ARM mode [...] tmp.312625562.c:1:0: error: target CPU does not support ARM mode int main(void){} ^ He always create tmp file at the folder root whith nothing else than int main(void) {} inside. I did NOT change anything and everything was working fine yesterday.. Thanks, -- Maximin COSTE-LEENHARDT

2 1

Region overflow in bootstrap
by Markus Partheymueller 04 Jun '13

04 Jun '13

When booting Fiasco/L4Re on my test machine (16G RAM, quad-core i7), I get the following error message, unless I have all CPUs and HyperThreading active: L4 Bootstrapper Build: #2 Mon Jun 3 14:15:47 CEST 2013, x86-32, 4.8.0 Limiting 'RAM' region [100000000, 43e5fffff] {33e600000} to [100000000, 10ea803ff] { ea80400} due to 3024 MB limit Bootstrap: add_nolimitcheck: Region overflow As soon as I deactivate CPUs in the BIOS or deactivate HT, it fails. Increasing the buffer __ram[8] to, e.g., __ram[16] in bootstrap/server/src/startup.cc:L67 does the trick. Maybe that buffer is too small for some machines?

2 1

All *.cpp files are ignored by Makefile
by BogDan 02 Jun '13

02 Jun '13

Hi, I tried to add a few .cpp files to Makefile but it seems that L4Re build systems ignores this extension. This is the content of the Makefile: #################################### PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = test_cpp SRC_CC = main.cpp class1.cpp class2.cpp REQUIRES_LIBS = libstdc++ include $(L4DIR)/mk/prog.mk #################################### I tried to replace SRC_CC with SRC_CXX or SRC_CPP but with no luck ... This bug prevents the port of most of C++ libs out there to L4Re. BTW, is there any chance to use other build-systems (cmake, qbs, premake, SCons, etc.) to build L4Re libs/apps ? Cheers, BogDan.

3 5

How to catch unhandled exceptions ?
by BogDan 02 Jun '13

02 Jun '13

Hi, Is there any way to catch all system unhandled exceptions (seg fault, fpu fault, etc.) and "transform" them into C++ exceptions ? I tried to use a combination of "L4::Thread::control" with "L4::Thread::Attr::exc_handler" to catch the system exception but it didn't worked for me, most probably I didn't understood the meaning of "l4_thread_control_exc_handler" or how to use it. Any example/help will be very appreciated. Of course, after I'll catch the exception, I need a way to "resume" the thread execution to another ip (address) which actually is a simple function that throws the C++ exception, any example/help on the matter will also be highly appreciated. Cheers, BogDan.

2 2

Can't use cxx::Thread
by BogDan 02 Jun '13

02 Jun '13

Hello, I tried to create a very simple application that uses cxx::Thread, but I have some link problems: ... Compiling main.o ==> Linking test_cxx_thread main.o:(.rodata._ZTI10TestThread[_ZTI10TestThread]+0x8): undefined reference to `typeinfo for cxx::Thread' Also I think it will be cleaner/better for developers if run, execute and shutdown methods will be moved to a protected section. This is the main.cc content: /////////////////////////////////////////////// #include <iostream> #include <l4/cxx/thread> #include <thread> class TestThread : public cxx::Thread { public: TestThread():cxx::Thread(true){} private: virtual void run() { std::cout << "TestThread" << std::endl; } }; static void TestStdThread(int param) { std::cout << "TestStdThread param:" << param << std::endl; } int main(int argc, char ** argv) { (void)argc; (void)argv; TestThread cxxTh; cxxTh.start(); std::thread stdTh(TestStdThread, 1); for (;;) { std::cout << "Hello World!" << std::endl; sleep( 1 ); } stdTh.join(); } /////////////////////////////////////////////// This is the Makefile content: #################################### PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = test_cxx_thread SRC_CC = main.cc CXXFLAGS += -std=c++11 REQUIRES_LIBS = cxx_thread cxx_libc_io cxx_io libstdc++ libpthread include $(L4DIR)/mk/prog.mk #################################### Yours, BogDan.

2 2

Kernel debugger in MP mode causes double fault
by Markus Partheymueller 01 Jun '13

01 Jun '13

Hi folks, has anyone tried to invoke the kernel debugger in a multiprocessor setup? When I boot the demo scenario in qemu with qemu -smp 2 -cpu core2duo and then hit Escape, the system crashes with a double fault. Without smp or with -cpu qemu32 the problem doesn't occur. Can someone confirm this issue or give a hint what could be wrong? Cheers Markus

2 1

L4Re: FATAL: Exception Operation not permitted: ''"
by Maximin Coste 01 Jun '13

01 Jun '13

Hi, I'm running an edited and "old" (September 2012) version of L4Linux & uC-OS/II in top of Fiasco+L4RE (updated here). When launching the image I have generated, I have the following error: MOE: cmdline: moe rom/l4lx_ucos.cfg MOE: Starting: rom/ned rom/l4lx_ucos.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx_ucos.cfg' Ucos | L4Re: FATAL: Exception Operation not permitted: '' Ucos | Exception: Operation not permitted: : backtrace ... l4linux | L4Re: FATAL: Exception Operation not permitted: '' l4linux | Exception: Operation not permitted: : backtrace ... io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request. Can I see more about what's going wrong ? Can I see the backtrace those logs talks about ? :) -- Maximin COSTE-LEENHARDT

2 3

How to boot Fiasco microkernel on raspberry pi
by Rahul Singhal 31 May '13

31 May '13

I want to port Fiasco microkernel to RPi. I found that Fiasco now supports RPi. I am a newbie in this kernel field. I have compiled the L4 microkernel and the L4 runtime environment for RPi succesfully but I don't know how to use the generated binaries to run RPi. I am running on ubuntu 12.04. Could you please tell me the procedure and files to be put on the sd card of RPi so that it boots into the L4 runtime environment.

3 5

sigma0 memory space
by joel＠nider.org 31 May '13

31 May '13

I have been reading about the structure of L4Ka::Pistachio, and discovered that they use idempotent (1:1) page table mapping in their sigma0 process. I am wondering if Fiasco also takes this approach? If so, does the kernel also use idempotent mapping? I would imagine that this would have some implications on demand paging in the kernel. Does the kernel even use demand paging? (I mean at some point during boot the kernel will start to use memory to store kernel objects - either the kernel 'guesses' how much it will ever need and statically allocates that memory, or it's going to have to ask for pages later on, which will be owned by some other process). I tried to read the code, but found it very hard to traverse - the C++ classes don't make it easy to follow a flow. Can you please point out the file(s) where the kernel sets up the memory space for sigma0, and where it passes the initial ownership (from kernel space to sigma0 space)? Thanks, Joel

2 1

Building l4re packages and linking errors
by Bryce Cronkite-Ratcliff 13 May '13

13 May '13

Hi folks, I'm afraid my configuration may have changed recently, possibly due to version changes in gcc, and I'm having some trouble compiling l4re, so I wanted to ping you to see if you had any insights. Two separate issues I've had: in an existing l4re build, executing make in an individual package sub-directory fails to find basic system headers in included files ("stddef.h" and "stdarg.h" for example). I'm running make O=basel4rebuilddir On the theory that l4re needs to be recompiled in order to set up links that may have changed since compilation of the last build, I've tried building l4re again, but I similarly run into a linker problem here: gcc: symbol lookup error: /home/bryce/L4Linux/x86/l4re4/tool/gendep/64/libgendep.so: undefined symbol: dlsym If you have any thoughts on what I might try, let me know! Thank you! Bryce

2 2

Questions about Fiasco.OC and L4Re
by BogDan 13 May '13

13 May '13

Hello, First I'd like to introduce myself, I'm BogDan Vatra a free software hacker. Recently I've watched these http://wiki.tudos.org/HOWTOs#Introduction_to_Fiasco.OC_and_L4Re presentations on youtube. After I've seen them (many many times) I became fascinated. I started to "play" a little bit with Fiasco.OC and L4Re, I created a few apps and I must confess that I'm extremely impressed by your work. To me Fiasco.OC and L4Re seems way too good to be true, and I wonder if there are any "hidden traps" which prevents people to use it to create a general-purpose operating system on top of Fiasco.OC and L4Re, so my first question is: Can Fiasco.OC and L4Re be used to create free (GPL, BSD, apache, etc.) and non-free apps? I checked L4Re licenses and it seems that it has the necessary exceptions, but I'd like to be 100% sure :). I also look to Genode frameowrk and I it looks to me that it cannot be used to create non-GPL apps, so, it can not be used to create a general-purpose operating system where any kind of apps can run on it. I also have a few questions about the completeness of Fiasco.OC and L4Re: - does L4Re have any OpenGL support? I checked the source code and it seems that the only way to do graphics is via goos and it doesn't seem to have any OpenGL support. If I am right wouldn't be easier to port (and upstream) an existing server (e.g. xorg, wayland, mir, etc.) to L4Re, than to create one from scratch and maintain it? - does L4Re have any sound support? If it hasn't, then how hard will be to implement or to port an existing implementation? - does L4Re have any real filesystem support (e.g. ext2/3/4, xfs, raiser, etc.)? It is ok for testing to use qemu or grub to load simple apps, but for a real o.s., apps need to be loaded from disk. Again, if it hasn't, then how hard will to implement it or to port an existing implementation? - it is possible to use a debugger (e.g gdb(server)) to debug (user space) apps? - last but not least, is there any repository for Fiasco.OC and L4Re with logs? http://svn.tudos.org/repos/oc/tudos/trunk/ has no useful logs and IMHO it makes very hard any contribution to it. I've seen that you have a few repos on github (https://github.com/TUD-OS), do you have any plans to move Fiasco.OC and L4Re to github as well? IMHO being able to fork a repository and to create a pull request, to be able to open an issue and watch its progress will make contributors life much more easier :) ! Many thanks for your work! Yours, BogDan.

2 1

Question regarding the "Jdb::handle_user_request()' function
by Christian Prochaska 11 May '13

11 May '13

Hello, the 'Jdb::enter_jdb()' function in file 'jdb.cpp' contains the following code: // check for int $3 user debugging interface if (foreach_cpu(&handle_user_request, true)) { close_debug_console(cpu); leave_trap_handler(cpu); return 0; } I'm not sure why in this case the second argument of 'foreach_cpu()' is true. I understand that it causes the result to be true only if the 'handle_user_request()' function returned true for every currently running CPU. But I found that this can be a problem when using the '-jdb_cmd=JS' kernel argument: if only one CPU is currently running, the result of 'foreach_cpu()' is true, but when two CPUs are currently running, the 'handle_user_request()' function returns true only for one CPU, which makes the end result false and causes the kernel to stop with the JDB prompt shown. Can somebody please explain? Christian

2 4

fiasco r52 on beagleboard xm
by Sin-ta Hsiea 11 May '13

11 May '13

Hi, I've tried running r47 fiasco kernel on beagleboard xm platform, it was fine, but after upgrading sources to r52, it broke. Output message hang after this line. Hello from Startup::stage2 After debugged using JTAG, I found that after page table modified, MMU still can't translate that address. So I add this line to source: --- src/kern/arm/paging-arm.cpp (revision 52) +++ src/kern/arm/paging-arm.cpp (working copy) @@ -348,6 +348,7 @@ void Pte_ptr::write_back_if(bool, Mword asid = Mem_unit::Asid_invalid) { + Mem_unit::clean_dcache(pte); if (asid != Mem_unit::Asid_invalid) Mem_unit::tlb_flush(asid); } Then output message hang after this line: Calibrating timer loop... done. It seems that MMU doesn't notice page table was switched to sigma0's pagetable. I also tried pandaboard, it just works fine. Does anybody have idea how to fix this? Best regard, SIn-ta Hsiea

2 2

Fiasco.OC with ARM TrustZone
by Chao-Jui Chang 11 May '13

11 May '13

Hi hackers, Is trustzone working on exynos 4412 platform? I have selected the follow item in Fiasco config menu: * Platform Timer (Multi-core timer) * Use ExtGic * Execution Model (TrustZone normal side) But it stop at early stage. Same result for Execution Model (Standard mode). but no message for Execution Model (TrustZone secure side). If the trustzone is disabled in u-boot, the 'Standard mode' works fine. ----- booting log ----- OK U-Boot 2010.12-00000-g8d816e8-dirty (May 06 2013 - 19:38:10) for Exynox4412 CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 1023 MiB PMIC VERSION : 0x00, CHIP REV : 3 TrustZone Enabled BSP BL1 version: 20121128 Checking Boot Mode ... SDMMC MMC Device 0: 30959 MB MMC Device 1 not found ModeKey Check... run normal_boot Net: No ethernet found. Hit any key to stop autoboot: 0 Exynos4412 # run fiasco Partition2: Start Address(0x2000), Size(0x1a000) reading bootstrap.raw 835584 bytes read Boot with zImage Starting kernel ... Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0044588-0xf0044f60) Number of IRQs available at this GIC: 160 ------ end of booting log ----- Best regards, Chao-Jui

2 1

How to start new program in interactive way
by Chao-Jui Chang 02 May '13

02 May '13

Hi hacker, Is there any other way to start a new l4 program or l4linux? Currently, I can only start program by writing lua script. Can I start new program like in a shell environment? For example: $ ls -> run ls program $ df -> run df program If no shell like environment, is there any example by using L4Re API? Thanks, Chao-Jui

2 1

Re: How to start 2 or more VMs
by Chao-Jui Chang 29 Apr '13

29 Apr '13

Hi Ganis Zulfa, You need to setup one ethX for each l4linux. When you start 2 L4Linuxes, you will only see one ethX in current console, because you are connected to the second L4Linux not the first one. It is normal to see only one ethX. One way to setup the ip of first L4Linux is to write the init config in /etc/init.d/rcS. In this case, you need 2 ramdisk for each L4Linux. Here is my config for first L4Linux: # cat /etc/init.d/rcS > #! /bin/sh > mount -t proc proc /proc > mount -t devtmpfs devtmpfs /dev > mkdir /dev/pts > mount -t devpts devpts /dev/pts > ifconfig lo up > ifconfig eth0 192.168.50.1 > telnetd -l /bin/sh > exit 0 For second L4Linux, just change the ip to 192.168.50.2 After 2 L4Linuxes start, you will be in second L4Linux(192.168.50.2) then, you can telnet 192.168.50.1 to go to another L4Linux. Cheers, Chao-Jui 2013/4/16 Ganis Zulfa Santoso <ganiszulfa(a)gmail.com> > Hi Chao-Jui, have u figured out a way to do what Adam said? > > I followed the instructions from http://wiki.tudos.org/L4Linux/shmnet, > but I have problems: > > A. i ran two l4linux arms but i only found one ethX > > B. how do i set up the ip of another l4linux arm? > > thanks. > > > Best regards, > > > Ganis Zulfa Santoso > > > On Mon, Apr 8, 2013 at 7:03 AM, Adam Lackorzynski < > adam(a)os.inf.tu-dresden.de> wrote: > >> Hi, >> >> On Fri Apr 05, 2013 at 13:29:37 +0800, Chao-Jui Chang wrote: >> > Is it possible to multiplex multiple text-based console? >> > I want to try to start multiple VMs on ARM board which only provides >> serial >> > console. >> >> You can connect two L4Linuxes using a l4shmnet-based local network >> connection, so you can go from one to the other via e.g. telnet or ssh. >> >> >> Adam >> -- >> Adam adam(a)os.inf.tu-dresden.de >> Lackorzynski http://os.inf.tu-dresden.de/~adam/ >> >> _______________________________________________ >> l4-hackers mailing list >> l4-hackers(a)os.inf.tu-dresden.de >> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >> > >

3 4

2025

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