- l4-hackers - example.com Site

Some confusing code of the kernel
by Yuxin Ren 01 Jun '14

01 Jun '14

Hi, Now I am learning the kernel code of Fiasco. But as I do not know much about C++, I feel confused about some code. In the file obj_space-virt.cpp, we have such code EXTENSION class Generic_obj_space : Obj_space_virt<Generic_obj_space<SPACE> > And similarly, in the file obj_space-phys.cpp, we have EXTENSION class Generic_obj_space : Obj_space_phys<Generic_obj_space< SPACE > > 1. What's the meaning of these tow line code? Does it mean that the class Generic_obj_space inherit from both class Obj_space_virt and class Obj_space_phys? 2. I note that class Obj_space_virt and Obj_space_phys have some methods with the same name, such as lookup_local method. When such a method is called, how can I know which class is invoked? Thanks a lot.

4 7

page fault on virtual bus
by ba_f 30 May '14

30 May '14

Hello Hackers, i try to access some peripheral on my platform. But i get page faults when writing to the peripheral at 0x41220000: MOE: Hello world MOE: found 505476 KByte free memory MOE: found RAM from 6f000 to 1f000000 MOE: allocated 495 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [116d000-116d117] [C:503000] periTest.cfg BOOTFS: [116e000-116e1aa] [C:504000] periTest.io BOOTFS: [116f000-1188494] [C:505000] l4re BOOTFS: [1189000-129673c] [C:506000] io BOOTFS: [1100000-1152c0c] [C:507000] ned BOOTFS: [1153000-116c5e4] [C:508000] periTest MOE: cmdline: moe rom/periTest.cfg MOE: Starting: rom/ned rom/periTest.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/periTest.cfg' periTest| L4Re[rm]: unhandled write page fault @41220000 pc=1000294 periTest| L4Re: unhandled exception: pc=0x1000294 Here is my CFG. My io-file looks like the one here https://os.inf.tu-dresden.de/L4Re/doc/io.html ## cfg require("L4"); local loader = L4.default_loader; local io_buses = { FOODEVICE = loader:new_channel(); }; loader:start({ caps ={ FOODEVICE = io_buses.FOODEVICE:svr(), }, }, "rom/periTest rom/periTest.io" ); ## end CFG Thanks for any help.

4 3

Re: kinvoke fonction
by Matthias Lange 28 May '14

28 May '14

On Tue, May 27, 2014 at 03:45:18PM +0000, Bouchra Elouri wrote: > Hi Matthias, > can you explain to me what this fonction do :Scheduler::kinvoke(L4_obj_ref > ref, L4_fpage::Rights rights, Syscall_frame *f, Utcb const *iutcb, Utcb > *outcb) > > L4_obj_ref ref : ?? explication L4_obj_ref is a reference to a kernel object. See src/abi/l4_types.cpp for details. > L4_fpage::Rights rights : ?? These are the access rights for the kernel object. See src/abi/l4_fpage.cpp. > Syscall_frame *f : ?? A Syscall_frame encapsulates the system call data. See src/kern/entry_frame.cpp. > Utcb const *iutcb, Utcb *outcb: ?? The UTCB is used to pass and return data between kernel and user (in case of a system call) or between IPC partners. If you have other questions in the future please use the l4-hackers mailing list! Matthias. -- 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

[Question] How do I do to secure LCD on L4 Linux ?
by Yeongchan 28 May '14

28 May '14

Hi, l4hackers I'm try to securing LCD on L4 Linux using Freescale i.MX6Q SABRESD board. I succeeded in securing Ethernet on L4 Linux. But I don't yet secure LCD on L4 Linux. LCD(HSD100PXN1) is connected by LVDS. I've modified as below.. 1.' .io' I've added LDB control register address to '.io' file. 2. 'mach_setup.c' (l4linux/arch/l4/kernel/arch-arm/mach_setup.c) I've added code for LVDS. Qusetion 1. Did I do wrong modification ? Qusetion 2. Must I do something outside of that ? How do I do to secure LCD on L4 Linux ? If you give a bit hints me, I would appreciate it .

2 1

Re: Doing simple I/O in clntsrv example
by Marcus Hähnel 26 May '14

26 May '14

On 2014-05-22 16:02, Valentin Hauner wrote: > On 05/22/2014 03:41 PM, Marcus Hähnel wrote: >> Sorry. Forgot to reply to the previous mail. Is this for a 64-bit or >> 32-bit system? > No problem. > It's a 32-bit system, I'm compiling into ./bin/x86_586. You need a terminal to do input. fbterminal is one that provides what you need. It does not work from the serial line out of the box as far as I know. Please have a look at the x86-fb.* example in l4/conf/examples and start the client using the same method. This will allow it to receive keyboard input. Instead of the ex_spectrum... example use fbterminal to start with mag using (for example) the following lines: local c = { fb = mag_caps.svc:create(L4.Proto.Goos, "g=800x600"), term = l:new_channel():svr() }; l:start({ caps = c }, "rom/fbterminal"); And then start the clntsrv-client in the terminal using (again, for example): l:startv({ caps = { calc_server = calc_server}, log = c.term:m("ro") }, "rom/ex_clntsrv-client"); Best regards, - Marcus Haehnel

1 0

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