l4-hackers

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

2827 discussions

l4re compilation
by Ramya Masti 04 Jun '14

04 Jun '14

Hi all, I am trying to compile l4re run time from the snapshot (l4re-snapshot- 2014053111) using GCC 4.9 on an x86-64 machine with multilib. The compilation fails with not being able to find cstdio header file. I followed the instructions in http://os.inf.tu-dresden.de/L4Re/build.html. I note that the fiasco kernel itself builds fine from the same snapshot. Some debug information: -------------------------------------------- Output of gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/gcc-multilib/src/gcc-4.9-20140507/configure -- prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ -- enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared -- enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable- libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable- libssp --enable-gnu-unique-object --enable-linker-build-id --enable-cloog- backend=isl --disable-cloog-version-check --enable-lto --enable-plugin -- enable-install-libiberty --with-linker-hash-style=gnu --enable-multilib -- disable-werror --enable-checking=release Thread model: posix gcc version 4.9.0 20140507 (prerelease) (GCC) ---------------------------------------------- Output of make O=build in the src/l4 directory (of what I think maybe relevant parts) === Building package "libstdc++-headers" === bash: line 0: cd: /home/ramya/Downloads/fiasco/l4re-snapshot- 2014053111/src/l4/pkg/libstdc++-headers/../libstdc++-v3/contrib/libstdc++- v3-/include: No such file or directory ....... ....... ....... ....... ....... ....... === Building package "cxx_libc_io" === ... Compiling io_backend.o /home/ramya/Downloads/fiasco/l4re-snapshot- 2014053111/src/l4/pkg/cxx_libc_io/lib/src/io_backend.cc:9:18: fatal error: cstdio: No such file or directory #include <cstdio> ^ compilation terminated. Is this a problem with the GCC version? Any help is much appreciated. Best, Ramya

2 2

Documentation of Sched_context
by Valentin Hauner 03 Jun '14

03 Jun '14

Hi, what exactly is represented by a Sched_context? 'sched_context-fixed_prio.cpp', for example, contains members called '_prio' and '_quantum'. That would suggest that a Sched_context is a schedulable object like a task or a thread. However, the file mentioned above defines some sort of ready queue, too. That would indicate that a Sched_context is some part of the scheduler that organizes the schedulable objects in a data structure? Where are all those classes documentated? Using the search box, the official documentation (http://os.inf.tu-dresden.de/L4Re/doc/index.html) does not offer any information about these. Best regards, Valentin Hauner

2 1

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers