l4-hackers March 2012

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

20 participants
20 discussions

L4Android and L4Linux parallel on an i.MX53
by Tobias Fink 22 Apr '12

22 Apr '12

Hello List, for my bachelor project I'm trying to run Android and Linux parallel on an i.MX53 Board. While the first approach with KVM seemed not to be the right way to go L4 looks promising. While I found many interesting and helpful topics in this list I still have some questions. I tried to first build the "Hello World" example which worked fine but failed in building other examples because of not fulfilled dependencies (first to note io). I already checked out "l4linux_requirements". What else do I need? The board is a custom board with very little documentation. I have some Linux drivers for the connected hardware. Is it possible to use them with L4Linux or would I have to get/write drivers for L4 itself? Sorry about these very basic questions. I've just started working with L4. Regards Tobi

4 9

shmc/l4shmnet improvements
by Stefan Fritsch 17 Apr '12

17 Apr '12

Hi, the attached shmc.diff fixes many bugs in shmc and adds some new functionality. l4shmnet.diff then uses this to implement a protocol that does not require one end to wait for the other end during boot, and that allows to set the link state up and down. The old protocol is still supported. The changes may be used under the MIT license (which is included in the include/shmbuf.h file. You can find the detailed changelog for shmc.diff below. The diff is on top of the diff I have sent in November. Cheers, Stefan Add include/shmbuf.h which implements the l4shmnet packet protocol, to be used by l4linux and others. include/shmc.h: - l4shmc_iterate_chunk(): New function to iterate over all chunk names - l4shmc_chunk_size(): change return value to allow returning an error - l4shmc_area_size_free(): New function to get remaining free space - l4shmc_area_overhead(): New function to get overhead not usable by chunks - l4shmc_chunk_overhead(): New function to get size overhead per chunk include/types.h: - Make l4shmc_chunk_desc_t members volatile to avoid races - l4shmc_area_t: add _size member for fast access - l4shmc_chunk_t: add _capacity member that stores the size outside of the shm area and is therefore safe from tampering by remote end shmc/include/internal.h: - l4shmc_chunk_ready(): need HW memory barrier - l4shmc_chunk_size(): Check for overflow - l4shmc_chunk_capacity() adapt to new _capacity member - l4shmc_chunk_consumed(): don't need a memory barrier lib/src/shmc.c: - l4shmc_create(): protect from integer overflows, initialize lock - l4shmc_area_overhead(): new function - l4shmc_chunk_overhead(): new function - next_chunk(): utility function that gets the next chunk, with proper sanity checks to avoid invalid memory access/loops if the other side is malicious - l4chmc_iterate_chunk(): new function - l4shmc_add_chunk(): Add sanity checks, use next_chunk(), initialize complete chunk struct properly before inserting into linked list - l4shmc_area_size_free(): new function - l4shmc_get_chunk_to(): Add sanity checks, use next_chunk()

2 4

Bind irq to icu failed
by Shashi Sharma 09 Apr '12

09 Apr '12

Hi, I am trying to use e1000e driver in Ankh to bring-up intel's 82574L ethernet controller. But its unable to allocate interrupt and I cant figure out the source of the problem. Here is the ankh log: ------------------------------------------------------------------------ ankh | Initialized DDELinux 2.6 ankh | Initializing DDE page cache ankh | ddekit_pci_init ankh | pci bus constructor ankh | PCI: L4 root bridge is device 4e768 ankh | init_wq_head ankh | l4dde26_register_rx_callback: New rx callback @ 0x1000270. ankh | Softirq daemon starting ankh | <6>e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 ankh | <6>e1000e: Copyright (c) 1999-2008 Intel Corporation. ankh | unimplemented: pci_set_master ankh | <3>0000:00:01.0: 0000:00:01.0: Failed to initialize MSI-X interrupts. Falling back to MSI interrupts. ankh | <3>0000:00:01.0: 0000:00:01.0: Failed to initialize MSI interrupts. Falling back to legacy interrupts. ankh | <6>0000:00:01.0: eth0: (PCI Express:2.5GB/s:Width x1) 0x14815cM ankh | <6>0000:00:01.0: eth0: Intel(R) PRO/1000 Network Connection ankh | <6>0000:00:01.0: eth0: MAC: 3, PHY: 8, PBA No: ffffff-0ff ankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI ankh | <6>Copyright (c) 1999-2006 Intel Corporation. ankh | <6>net_namespace: 636 bytes ankh | open_network_devices() ankh | opening lo ankh | <6>device lo entered promiscuous mode ankh | set interface to promiscuous mode. ankh | opening eth0 ankh | <6>device eth0 entered promiscuous mode ankh | set interface to promiscuous mode. ankh | Thread 0xb0 for IRQ 10 ankh | Bind irq to icu failed with -2 ankh | claim_irq: failed to attach IRQ ankh | <3>0000:00:01.0: eth0: Unable to allocate interrupt, Error: -16 ankh | error opening eth0 : -16 ankh | Opened -16 network devices. ankh | lo IRQ: 0x00 MAC: 00:00:00:00:00:00 MTU: 16436 ankh | Registered @ registry. ankh | Gooood Morning Ankh-Morpoooooork! TID = 0x57 ankh | Creating session factory. ankh | Configuration: debug,promisc,device=eth0,shm=shm,bufsize=16384,phys_mac ankh | Debug mode ON. ankh | Using promiscuous mode. ankh | Device 'eth0' requested. ankh | SHM area 'shm' requested. ankh | Buffer size: 16384 ankh | Physical MAC requested. ankh | rom/ankh: /home/shashi/Desktop/L4/src/l4/pkg/ankh/server/src/session: 159: Ankh::ServerSession::ServerSession(bool, bool, bool, const char*, const char*, unsigned int. bool): Assertion `_dev' failed. --------------------------------------------------------------------------------------- I appreciate your help. Regards, Shashi

4 8

ARM and PCI?
by Stefan Fritsch 02 Apr '12

02 Apr '12

Hi, do you know what remains to be done to use PCI on ARM (e.g. Realview in qemu) with L4Re and IO? I guess that io needs some changes to support PCI-IO-Ports mapped into memory. Or should that already work? Cheers, Stefan

2 1

Granting flex pages in Fiasco.OC / L4Re
by Daniel Waddington 30 Mar '12

30 Mar '12

Hi, I am using l4_task_map to map flex pages to a child task. What I would like to do is grant a flex page to a child and remove the mapping from the parent. How do I do this? I have tried using l4_map_obj_control(0,1) for mr[3] on the task map call but this does not seem to help. Thanks in advance, Daniel

3 4

TUD:OS releases DDEKit/Linux
by Hannes Weisbach 30 Mar '12

30 Mar '12

Hi all, DDEKit/Linux was released! DDEKit/Linux uses the Device Driver Environment approach to run dde-linux-2.6 in Linux user space. This allows Linux device drivers to run in Linux user space, including interrupt handling and DMA support. DDEKit/Linux was evaluated using an Intel E1000E NIC and it was possible to saturate an 1GBit/s link. The source code, including dde-linux-2.6 and an E1000E-example are available for download at: http://os.inf.tu-dresden.de/ddekit Best regards, Hannes Weisbach

2 1

[l4linux+ankh] no eth0
by Timur 26 Mar '12

26 Mar '12

Hi all, i,m trying to bind l4linux to ankh. After launching with attached config files, l4linux doesn't see eth0 interface. What am i doing wrong? Log attached. [modules.list] entry L4Linux-mag-x86 roottask moe rom/l4lx-gfx.cfg module l4re module ned module l4lx-gfx.cfg module io module ankh module ankh.vbus module fb-drv module mag module x86-legacy.devs module l4lx-x86.io module vmlinuz module drops-rd.rd -- Galiullin Timur

4 5

Re: Issues with booting L4Linux
by Adam Lackorzynski 26 Mar '12

26 Mar '12

Hi On Thu Mar 22, 2012 at 18:28:17 +0100, Oliver Horst wrote: > I'm currently trying to setup a small test scenario where L4Linux runs in > parallel > with L4Android within Qemu. I managed to build and start L4Android and it > works fine. > However, I didn't succeeded with booting L4Linux, again the build process > worked out > flawlessly, but the boot process quits with the following message: > > vmlinuz | Invalid IO-Port access at pc = 005b9cec port=0x1f7 > vmlinuz | Page fault (non-resolved): pfa=1a8 pc=4947ad > Die message: Trap: 14 > vmlinuz | panic: going to sleep forever, bye This is the IDE driver trying to accses the hardware, and it is not allowed to do so. For your use-case, just disable everything with IDE in the config name in L4Linux. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Trustzone & Fiasco.OC
by Stefan Kalkowski 23 Mar '12

23 Mar '12

Hello l4-hackers, I'd like to investigate the VM functionality for ARM's TrustZone in Fiasco.OC. I've read the paper of Torsten Frenzel et al. which covers experiments done with ARM TrustZone in Fiasco as a virtualization technique. In that paper they reference a VMM controlling the "normal world" VM(s), but unfortunately I cannot find it in the L4Re or L4Env tree. Is it publicly available, and if so could you please direct me to the right place? Thank you in advance & best regards Stefan -- Stefan Kalkowski 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 2

Issues with booting L4Linux
by Oliver Horst 22 Mar '12

22 Mar '12

Hi All, I'm currently trying to setup a small test scenario where L4Linux runs in parallel with L4Android within Qemu. I managed to build and start L4Android and it works fine. However, I didn't succeeded with booting L4Linux, again the build process worked out flawlessly, but the boot process quits with the following message: vmlinuz | Invalid IO-Port access at pc = 005b9cec port=0x1f7 vmlinuz | Page fault (non-resolved): pfa=1a8 pc=4947ad Die message: Trap: 14 vmlinuz | panic: going to sleep forever, bye I followed the diverse tutorials on the web and built Fiasco.OC, as well as L4Re with their default configurations. In case of L4Linux I tried the default configurations generated by the make targets 'x86-mp_vPCI_defconfig' and 'x86-native_defconfig', both with the same result as above. Please find attached my L4 startup files and the output log for the x86-mp_vPCI_defconfig variant. My Qemu execution command looks like the following: $ qemu -cdrom images/l4linux-x86.iso -boot d -m 512 -serial stdio -enable-kvm Do you have any suggestions how to solve this issue? Best Regards Oliver

1 0

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 March 2012