- l4-hackers - example.com Site

where can I download the previous version of L4linux?
by li94575 06 Jul '16

06 Jul '16

Hi, I want to use L4linux3.5 and L4linux3.10, but L4linux SVN repository and l4re-snapshot both are the latest release. Can anyone tell me where to download it? Thank you!

2 3

l4re-snapshot-2016060908 lunch "L4Linux-mag-x86" problem
by 张鑫 04 Jul '16

04 Jul '16

Hi, Everyone, I'm a newer in L4Linux,I get the lastest snapshort and follow the README which builds it successfully, When I execute make qemu in /my_dir/obj/l4/x86 ,it comes up Entry selection , I tested all but "L4Linux-mag-x86" is'nt work successfully. I prebuild the snapshot in Ubuntu 14.04.4 LTS, the following is the ubuntu output message: L4 Bootstrapper Build: #1 Fri Jul 1 02:18:27 PDT 2016, x86-32, 4.8.4 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1424 bytes to copy MBI reserved 1424 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 3013400-33133ff } -> { 3e32000-4131fff } [3145728] moving module 11 { 2b28400-3012aa4 } -> { 3947000-3e316a4 } [5154469] moving module 10 { 2b27400-2b2765e } -> { 3946000-394625e } [607] moving module 09 { 2b26400-2b26737 } -> { 3945000-3945337 } [824] moving module 08 { 24e6400-2b25ab7 } -> { 3305000-39446b7 } [6551224] moving module 07 { 2209400-24e5ebb } -> { 3028000-3304abb } [3001020] moving module 06 { e86400-2208973 } -> { 1ca5000-3027573 } [20456820] moving module 05 { e85400-e8591b } -> { 1ca4000-1ca451b } [1308] moving module 04 { b24400-e846a5 } -> { 1943000-1ca32a5 } [3539622] moving module 03 { 968400-b23b8f } -> { 1787000-194278f } [1816464] moving module 02 { 41e400-967f0a } -> { 123d000-1786b0a } [5544715] moving module 01 { 378400-41dcbf } -> { 1197000-123c8bf } [678080] moving module 00 { 2e1400-378257 } -> { 1100000-1196e57 } [618072] Loading /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco Loading re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 2000, 258f] { 590} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10f193] { f194} Sigma0 re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 17c367] { 3c368} Root /l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 400000, 49bfff] { 9c000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 1787000, 4131fff] { 29ab000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001d4 sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco at 003007c0 Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on ia32 Rev: unknown compiled with gcc 4.8.4 for Intel Pentium [] Build: #1 Fri Jul 1 02:13:30 PDT 2016 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI: RSDP[0xf0990] r00 OEM:BOCHS. Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector f8 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 3397MHz 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. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:110000;13ffff] [4:140000;17cfff] [0:17d000;3fffff] [0:495000;1786fff] [4:1787000;4131fff] [0:4132000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 197224 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [1787000-1942790] [C:105000] l4re BOOTFS: [1943000-1ca32a6] [C:107000] ned BOOTFS: [1ca4000-1ca451c] [C:109000] l4lx-gfx.cfg BOOTFS: [1ca5000-3027574] [C:10b000] io BOOTFS: [3028000-3304abc] [C:10d000] fb-drv BOOTFS: [3305000-39446b8] [C:10f000] mag BOOTFS: [3945000-3945338] [C:111000] x86-legacy.devs BOOTFS: [3946000-394625f] [C:113000] l4lx-x86.io BOOTFS: [3947000-3e316a5] [C:115000] vmlinuz BOOTFS: [3e32000-4132000] [C:117000] ramdisk-x86.rd MOE: cmdline: /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f0990 io | ACPI: RSDP 0x00000000000F0990 000014 (v00 BOCHS ) io | ACPI: RSDT 0x000000000FFFFBC1 000034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x000000000FFFF1C0 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x000000000FFFE040 001180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0x000000000FFFE000 000040 io | ACPI: SSDT 0x000000000FFFF234 0008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x000000000FFFFB11 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x000000000FFFFB89 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | io | Initializing Namespace objects: io | Table [DSDT: BXPCDSDT] (id 01) - 144 Objects with 18 Devices, 8 Regions, 52 Methods (6/46/5 Serial/Non/Cvt) io | Table [SSDT: BXPCSSDT] (id 02) - 155 Objects with 32 Devices, 1 Regions, 42 Methods (0/42/0 Serial/Non/Cvt) io | ACPI: 2 ACPI AML tables successfully acquired and loaded io | io | Completing Region/Field/Buffer/Package initialization: io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | evxfevnt-0182 Enable : Transition to ACPI mode successful io | Initializing General Purpose Events (GPEs): io | Initialized GPE 00 to 0F [_GPE] 2 regs on interrupt 0x9 (SCI) io | Initializing Device/Processor/Thermal objects and executing _INI/_STA methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20160318, System in ACPI MODE, 32bit timer io | ACPI Error: Could not enable PowerButton event (20160318/evxfevnt-304) io | ACPI Warning: Could not enable fixed event - PowerButton (2) (20160318/evxface-821) io | ACPI: could not register power-button handler: AE_NO_HARDWARE_RESPONSE io | ACPI: Enabled 16 GPEs in block 00 to 0F io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 200000 - 600000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 mag | pos: 0x0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2):5(11):6(5):5(0):0(0) mag | memory 0x400000 - 0x800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started 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 PH 0 offs=00001000 flags=r-x PH-type=0x1 virt=00100000 evirt=00473000 phys=00100000 ephys=00473000 f_sz=00373000 memsz=00373000 PH 1 offs=00374000 flags=rw- PH-type=0x1 virt=00473000 evirt=00573000 phys=00473000 ephys=00573000 f_sz=00052afe memsz=00100000 PH 2 offs=002b708c flags=--- PH-type=0x4 virt=003b608c evirt=003b60b0 phys=003b608c ephys=003b60b0 f_sz=00000024 memsz=00000024 Starting binary at 0x100000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80008c0 ======> L4Linux starting... <======== Linux version 4.6.0-l4 (zhangxin@ubuntu) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 Fri Jul 1 02:34:46 PDT 2016 Binary name: rom/vmlinuz Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 CPU mapping (l:p)[1]: 0:0 Image: 00100000 - 00573000 [4556 KiB]. Areas: Text: 00100000 - 003b5a5b [2774kB] RO-Data: 003b7000 - 00473000 [752kB] Data: 00473000 - 0049a500 [157kB] Init: 0049c000 - 004c6000 [168kB] BSS: 004c6000 - 0055d000 [604kB] gs=43 fs=43 Device scan: Device: L4ICU Device: PCI0 Device: pci_l4x[1] IRQ: 0000000b - 0000000b MEM: febc0000 - febdffff PORT: 0000c000 - 0000c03f DMAD: 00000000 - 00000000 Device: pci_l4x[2] PORT: 0000c040 - 0000c04f DMAD: 00000000 - 00000000 PORT: 000001f0 - 000001f7 PORT: 000003f6 - 000003f6 IRQ: 0000000e - 0000000e PORT: 00000170 - 00000177 PORT: 00000376 - 00000376 IRQ: 0000000f - 0000000f Device scan done. l4x_fiasco_gdt_entry_offset = 9 l4lx_thread_create: Created thread 41e (cpu0) (u:b3000e00, v:b3000c00, sp:00475fac) main thread will be 41e section-with-init(-data): Virt: 0x473000 to 0x572fff [1024 KiB] section-with-init(-data): Phys: 0x00298000 to 0x00397fff, [1024 KiB] section-with-init-text: Virt: 0x473000 to 0x572fff [1024 KiB] *error: failed to get physical address for 473000.* Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 00000000 Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] Main memory: Phys: 0x04400000 to 0x083fffff, [65536 KiB] l4x: vmalloc area: 04800000 - 0c800000 Filling lower ptabs... Done (254 entries). text: Virt: 0x100000 to 0x472fff [3532 KiB] text: Phys: 0x00495000 to 0x00807fff, [3532 KiB] Loading: rom/ramdisk-x86.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 0ca1b000 to 0cd1b000 [3072KiB] l4lx_thread_create: Created thread 425 (timer0) (u:b3000a00, v:00000000, sp:004f5fa8) WARNING: Unknown rdmsr: 00000186 at 0x4a4737 WARNING: Unknown rdmsr: 00000187 at 0x4a4737 WARNING: Unknown rdmsr: 000000c2 at 0x4a47f0 WARNING: Unknown wrmsr: 000000c2 at 0x4a480e WARNING: Unknown rdmsr: 000000c2 at 0x4a4814 the qemu out stop here: I find the error,But I have no idea about, can anybody help me ? Thanks in advanced! Best Reagrds！ ryan.zhang

1 0

building fiasco on alpine linux
by Michael Schnupp 27 Jun '16

27 Jun '16

Hi, I tried to build fiasco on alpine linux. This will fail with the following line: auto/jdb_ktrace.cc:1:0: error: code model kernel does not support PIC mode Their gcc enables PIC per default for security reasons. Since fiasco seems to need PIC disabled I have to tell the build system either to add -fno-PIC explictly, or to -D__KERNEL__ in any way. (I already tried DEFINES += -D__KERNEL__ or CFLAGS := -fno-PIC in Makeconf without success.) What is the correct way to add such an option to the fiasco build system? Would it hurt to add -D__KERNEL__ per default on future releases? (After all it *is* a kernel.) BTW, the above file looks very much like a jdb file. Is it correct that this file is compiled even when I configured fiasco to not include jdb? BR, Michael

2 6

Cross-compiling L4Re for MIPS32
by Paul Boddie 21 Jun '16

21 Jun '16

Hello, I finally got round to looking at L4/Fiasco.OC again, and having previously looked at the MIPS32 port that was made available on GitHub... https://github.com/MIPS/fiasco-l4re ...I have been attempting to cross-compile Fiasco and L4Re using the l4re.org sources. Getting Fiasco to cross-compile was mostly a matter of repeating the same procedure as last time: cd src/kernel/fiasco make BUILDDIR=mybuild cd mybuild/ make config make However, I needed to edit src/kernel/fiasco/src/Makeconf.mips32 to change the compiler settings. I'm using the toolchains in Debian unstable: CROSS_COMPILE ?= mipsel-linux-gnu- Previously, I used a Makeconf.local file to set the following: SYSTEM_TARGET=mipsel-linux-gnu- SHARED_FLAGS=-mips32r2 -EL -msoft-float -mno-abicalls -fno-pic Maybe the previous work used some different mechanisms to those used by the more general source distribution, but this trick didn't seem to influence the build successfully this time around. However, the build did complete successfully with the toolchain set appropriately. Meanwhile, I had more problems with the L4Re part. I had expected to be able to do the following: cd src/l4 make B=mybuild make O=mybuild config make O=mybuild E=mips-fbspectrum (The target was something that I had managed to build previously after some messing around with packages and configuration files. I'd managed to build the fbspectrum example for Fiasco.OC-UX, as the list archives will attest.) However, I also had to change the compiler settings (as done above) in src/l4/mk/arch/Makeconf.mips, instead of using src/l4/Makeconf.local (as done previously). Again, maybe the way of doing things was different in the previous incarnation of this port. I also needed to edit src/l4/tool/gendep/syscall.c to add a definition before unistd.h gets included: #define __ARCH_WANT_SYSCALL_NO_AT I can't remember if I or anyone else has mentioned this before now, but without it, things like __NR_open are not defined. Unfortunately, I haven't yet reached a satisfactory conclusion in this latter exercise. Looking back at my previous messages, it seems that a bit more work might be needed to configure and build a suitable target, and so I was wondering if anyone had done this (and written it up) for any of the MIPS boards, perhaps the CI20. Indeed, I wonder if things like the framebuffer are even supported for the CI20 or other MIPS boards. Paul

2 10

L4Linux Compilation trouble with missing packages in L4
by Martin Gruber 12 Jun '16

12 Jun '16

Dear L4 community, i started diving into L4 stuff recently and it looks really interesting. Currently I am trying to get L4Linux working on top of Fiasco.OC. After configuring the L4 Kernel, I am getting following error message at build: ---------------------------------------------------------------------------- make O=../build/ make[1]: Entering directory '/home/gruber/l4re/l4linux/build' Package shmc was not found in the pkg-config search path. Perhaps you should add the directory containing `shmc.pc' to the PKG_CONFIG_PATH environment variable No package 'shmc' found Package rtc was not found in the pkg-config search path. Perhaps you should add the directory containing `rtc.pc' to the PKG_CONFIG_PATH environment variable No package 'rtc' found Getting required compilation flags failed. L4OBJ: /home/gruber/l4re/src/l4/l4build L4_REQUIRED_MODS: libc_be_minimal_log_io libc_minimal libc_minimal_l4re libsupc++_minimal log l4re_c-util libio libvcpu shmc rtc arch/l4/Makefile:391: *** Aborting.. Stop. make[1]: Leaving directory '/home/gruber/l4re/l4linux/build' Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 ---------------------------------------------------------------------------- After checking the mailing list archive i found this question: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html I checked the l4/builddir/pc for missing libs and did not find them. Compilation of L4 worked fine, L4 also works with the small HelloWorld sample in QEMU. I checked the L4 config but was not able to find appropriate options. Does anyone have an tip for me what I am doing wrong? Thank you very much for your help! Kind Regards, Martin

2 1

Re: l4-hackers Digest, Vol 157, Issue 10
by Иван Филиппов 28 May '16

28 May '16

adam - maasdam ;-) 2016-05-28 13:00 GMT+03:00, l4-hackers-request(a)os.inf.tu-dresden.de <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. L4Re Release (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 27 May 2016 13:13:04 +0200 > From: Adam Lackorzynski <adam(a)l4re.org> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: L4Re Release > Message-ID: <20160527111304.GB12441(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > I'm happy to announce a new L4Re release. > > https://l4re.org/ > > This release adds support for the Imagination Technologies' > MIPS architecture, including support for MIPS' > virtualization architecture VZ to run virtual machines such > as Linux. L4Re is currently available for MIPS32, > MIPS64 is about to follow. The MIPS port is supported by > Imagination Technologies. > > > Further noteworthy changes of this release include: > - L4Linux has been updated to L4Linux-4.6 > - Conversion of debugging interface to capability-based > interface. Programs need to have the 'jdb' capability to > use JDB functionality. > - The virtual machines monitor, now called uvmm, supports > the MIPS and ARM architectures. > - A virtio-based peer-to-peer network component is available > in virtio-net. > - Documentation improvements > - Library updates > - Added ARM platforms: > - NXP Layerscape LS1021A > - i.MX28 > - MIPS platforms: > - Malta > - Sead3 > - Ci20 > - Baikal-T > - Bug fixes and small feature enhancements in the kernel and user-level > components: > - Added atomic IRQ re-attach call > - The vCPU data structures have been revised > > > Adam > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > ------------------------------ > > End of l4-hackers Digest, Vol 157, Issue 10 > ******************************************* > -- Иван Филиппов

1 0

L4Re Release
by Adam Lackorzynski 27 May '16

27 May '16

Hi, I'm happy to announce a new L4Re release. https://l4re.org/ This release adds support for the Imagination Technologies' MIPS architecture, including support for MIPS' virtualization architecture VZ to run virtual machines such as Linux. L4Re is currently available for MIPS32, MIPS64 is about to follow. The MIPS port is supported by Imagination Technologies. Further noteworthy changes of this release include: - L4Linux has been updated to L4Linux-4.6 - Conversion of debugging interface to capability-based interface. Programs need to have the 'jdb' capability to use JDB functionality. - The virtual machines monitor, now called uvmm, supports the MIPS and ARM architectures. - A virtio-based peer-to-peer network component is available in virtio-net. - Documentation improvements - Library updates - Added ARM platforms: - NXP Layerscape LS1021A - i.MX28 - MIPS platforms: - Malta - Sead3 - Ci20 - Baikal-T - Bug fixes and small feature enhancements in the kernel and user-level components: - Added atomic IRQ re-attach call - The vCPU data structures have been revised Adam

1 0

Flexpage: shared Mem
by ba_f 22 May '16

22 May '16

Hello, writing a L4Linux Driver I'm expiring the C-Interface and low level(?) flexpages. So far, I can push a Dataspace Capability via flexpage, and the receiving server is able to read its content. But, whatever the server writes in that mem-region doesn't appear on the clients side. /* client.c */ l4_fpage_t fpage = l4_obj_fpage( dataspace, 0, L4_CAP_FPAGE_RW ); l4_utcb_mr()->mr[0] = size; l4_utcb_br()->br[0] = fpage.raw; /* server.c */ l4_utcb_br()->br[0] = dataspace | L4_RCV_ITEM_SINGLE_CAP; l4_ipc_wait(l4_utcb(), 0, L4_IPC_NEVER); // allocate, and attach Dataspace ... // read & write Dataspace ... l4_utcb_mr()->mr[0] = returnValue; l4_ipc_reply_and_wait(l4_utcb(), l4_msgtag(0, 1, 0, 0), 0, L4_IPC_NEVER); As I am creating the fpage with L4_CAP_FPAGE_RW my guess was I can write to that mem-region and the client can read my changes. Anyway, maybe I need some more understandings about capabilities & flexpages. (Are there any precise slides or papers about this topic?) So, the client creates a dataspace capability and allocates some memory. But, what happens when the flexpage is pushed to the server? The capability is copied and both pointing to the same allocated memory, or is the Cap and(!) the memory it is pointing to copied to server? Thanks, ba_f

2 5

Question about Fiasco.OC support for SPARC
by deng.chao1＠zte.com.cn 11 May '16

11 May '16

Hi everyone： I want to run Fiasco.OS on SPARC-leon3 platform. It seems that Fiasco.OS already has an unimplemented support for SPARC-leon3 according to the latest snapshot fiasco-2015123115 of Fiasco. Does Fiasco.OS support SPARC now? If it does, how can I get the source? If it doesn't, what are the unimplemented parts according to snapshot fiasco-2015123115? And another question, is there any good machine emulator for SPARC-leon3？ I have tried latest version of QEMU, but It doesn't work well on SPARC-leon3. Thanks Dengchao

2 3

Task Priority Setting
by Nourhan Mohamed 02 May '16

02 May '16

Dear L4Hackers, I have been trying to run 2 simple L4 tasks and give one of them highest scheduling priority and the other one the least. I have tried using the priority attribute in the start script as well as: scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8) with different ranges for each of them but I don't notice any change in their runtimes. Am I missing something here? Thanks in advance, Nourhan

3 4