- l4-hackers - example.com Site

Porting Pistachio to Cell
by Tyson Key 22 Aug '19

22 Aug '19

Hi, In a wave of projects, over the years, I've been working on trying to rescue the Pistachio GitHub repository from bitrot, and build it with modern tools (I have one project that builds, and runs on x86, with an ancient version of GRUB, and another, that's a complete basket case, since KickStart is broken, but that's another matter), and saw, with some interest, ports to various Open Firmware-enabled platforms, and wondered if anyone had any guides to building, and running a PowerPC 64-bit userland, and boot infrastructure? There was an old guide to building with PSIM, and PPC32, on the KIT Website, but it seems incomplete, and it doesn't seem obvious, as to how one would build a bootable disk image, or how to prepare the compiled userland to run on hardware. Since the site is pretty dated, and the code has changed, since then, is that information even relevant? I've got access to a FreeBSD 12 PPC64 build environment, under QEMU's PSeries Xenial machine emulator, and I'm in the process of trying to set up a direct development environment, on a PlayStation 3 system, so access to PowerPC toolchains isn't a problem. Eventually, I'm planning on seeing if I can use the existing code, and parts of FreeBSD's PlayStation 3 port, to implement a basic, first-draft port to run on Sony's CellOS/BEAT ABI-based hypervisor, or in GameOS mode, with PetitBoot. Thanks in advance, for any assistance, Tyson Key.

1 0

New L4Re component released: virtio-net
by Jakub Jermar 29 Jul '19

29 Jul '19

Dear L4 hackers, last week we released virtio-net on GitHub[0]. Together with the previously released L4Re components, virtio-net can be used to interconnect two VMs with a virtual network. We also wrote a little tutorial which illustrates that[1]. Happy hacking, Jakub [0] https://github.com/kernkonzept/virtio-net [1] https://github.com/kernkonzept/manifest/wiki/MultipleVMs -- Kernkonzept GmbH at Dresden, Germany, HRB 31129, CEO Dr.-Ing. Michael Hohmuth

1 0

kernel error
by ssrmurthy saka 04 Jul '19

04 Jul '19

Hi team, I am using "4.13.0-36-generic" kernel and i exported cross compiler of version "gcc-linaro-7.4.1-2019.02-i686_arm-linux-gnueabihf". when i try to compile new odule i am facing below error. can you please help on this. make -C /lib/modules/4.13.0-36-generic/build/ M=/home/tessolve/c modules make[1]: Entering directory '/usr/src/linux-headers-4.13.0-36-generic' CC [M] /home/tessolve/c/vm.o In file included from ./include/asm-generic/int-ll64.h:10:0, from ./arch/arm/include/uapi/asm/types.h:4, from ./include/uapi/linux/types.h:4, from ./include/linux/compiler.h:231, from ./include/linux/init.h:4, from /home/tessolve/c/vm.c:1: ./include/uapi/asm-generic/int-ll64.h:11:10: fatal error: asm/bitsperlong.h: No such file or directory #include <asm/bitsperlong.h> ^~~~~~~~~~~~~~~~~~~ compilation terminated. scripts/Makefile.build:315: recipe for target '/home/tessolve/c/vm.o' failed make[2]: *** [/home/tessolve/c/vm.o] Error 1 Makefile:1550: recipe for target '_module_/home/tessolve/c' failed make[1]: *** [_module_/home/tessolve/c] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-36-generic' Makefile:4: recipe for target 'all' failed make: *** [all] Error 2 Thanks, murthy

1 0

Want to run L4Re on Raspberry PI.
by Lei Zhou 28 Jun '19

28 Jun '19

HI, I'm looking for the information and procedure how to compile and deploy L4Re on Raspberry PI. Any feedbacks would be greatly appreciated! Thanks, Lei

5 26

Enable L4Linux network access on Raspberry Pi-b.
by Lei Zhou 24 Jun '19

24 Jun '19

Hi Adam & Hackers, Has anybody enabled network access for L4linux Raspberry pi3? I read through all the history on related topics and understand the process to get it working. I summarized the steps as below and major problem for me is how to convert device tree for L4linux and compose corresponding rpi_deices.io configuration. Please see my specific question inlined in those steps. Thanks in advance for your feedback. 1. configure and Compile l4linux to support flattened device tree support. Also enables CONFIG_USB_LAN78XX=y && CONFIG_USB_USBNET=y CONFIG_USB_NET_SMSC95XX=y CONFIG_L4_SERVER = y CONFIG_USE_OF = y 2. Adapt https://github.com/raspberrypi/linux/blob/rpi-4.19.y/arch/arm/boot/dts/bcm2… into ./l4linux/arch/l4/boot/dts/simple.dts [Lei's question]: I understand why bcm2710-rpi-3-b.dts cannot be used directly because some of the reg_address physical address doesn't apply and might fail to be mapped. How can I pick network access specific device nodes and its dependancies(power or clock etc) and how to change those illegal reg_address? 3. Create an rpi3_devices.io for L4Re with the devices and their resources and assign the desired devices to a vbus. [Lei's question]: Should I define all device nodes one-2-one mapping from step 2's device tree? 4. Update your ned script and modules.list -- vim:set ft=lua: local L4 = require("L4"); loader = L4.default_loader; -- Start io vbus_l4linux = loader:new_channel(); --vbus_input = loader:new_channel(); --vbus_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 = vbus_input:svr(); l4linux = vbus_l4linux:svr(); -- fbdrv = vbus_fbdrv:svr(); }, log = {"IO", "y"}, l4re_dbg = L4.Dbg.Warn, }, "rom/io -vvv rom/rpi_devices.io"); -- Start L4linux loader:start( { caps = { -- fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = vbus_l4linux; }, log = L4.Env.log:m("rws"), l4re_dbg = L4.Dbg.Warn, }, "rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/ramdisk- l4x_dtb=rom/rpi3b-simple.dtb" .. L4.Info.arch() .. ".rd " .. "root=1:0 ramdisk_size=4000 init=/bin/sh earlyprintk=1 "); 5. Build final bootstrap_l4linux.uimage for Raspberry. Thanks very much! Lei Zhou

2 2

How to enable Guest Linux VM on Raspberry PI3?
by Lei Zhou 17 Jun '19

17 Jun '19

After I brought up L4Re and Fiasco on Raspberry PI3, would like to enable guest Linux VM on top of it. I'm looking at the link https://github.com/kernkonzept/manifest/wiki/LinuxVM and hoping I can do the same thing on Raspberry PI3. The link seems using hardware-assisted virtualization option uvmm based for guest VM. There seems also L4Linux Paravirtualization option. Which option should I use for me to enable guest LInux VM on Raspberry PI3? In addition, when I followed the link to try on QEMU first, encounter some "vbus" capability issue. I followed the guidance exactly as the link says. However, when I started the command to spawning the Linux VM as: $make E=uvmm-basic qemu It failed with following log: ============================================ MOE: virtual user address space [0-7fffffffff] MOE: rom name space cap -> [C:103000] MOE: rwfs name space cap -> [C:105000] BOOTFS: [41100000-411974b8] [C:107000] uvmm BOOTFS: [41198000-411c4e58] [C:109000] l4re BOOTFS: [411c5000-41246770] [C:10b000] ned BOOTFS: [41247000-412475c4] [C:10d000] virt-arm_virt.dtb BOOTFS: [41248000-41430200] [C:10f000] ramdisk-armv8.cpio.gz BOOTFS: [41431000-41431242] [C:111000] uvmm-basic.ned BOOTFS: [41432000-42618a00] [C:113000] Image.gz MOE: cmdline: moe rom/uvmm-basic.ned MOE: Starting: rom/ned rom/uvmm-basic.ned MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/uvmm-basic.ned' VMM[vmbus]: 'vbus' capability not found. Hardware access not possible for VM. VMM[main]: Hello out there. VMM: FATAL: ERROR: ARM GIC virtualization does not work without passing the virtual GICC via the vbus VMM[vm]: Device creation for virtual device virtio_uart@20000 failed. Disabling device. VMM[]: virtio_net(a)10000.l4vmm,virtiocap: capability net is invalid. VMM[vm]: Device creation for virtual device virtio_net@10000 failed. Disabling device. VMM: FATAL: ERROR: ARM GIC virtualization does not work without passing the virtual GICC via the vbus VMM[vm]: Device creation for virtual device interrupt-controller failed. Disabling device. VMM: FATAL: Parsing timer interrupt: Argument out of range qemu-system-aarch64: terminating on signal 2 Makefile:6: recipe for target 'do-all-make-goals' failed make: *** [do-all-make-goals] Interrupt ========================================================================= Any feedbacks are greatly appreciated! Lei Zhou

3 9

L4Re, BUILD_ARCH, cross-building for ARM on MIPS
by Paul Boddie 11 Jun '19

11 Jun '19

Hello, In attempting to investigate building L4Re/Fiasco.OC for the Raspberry Pi Zero, I encountered an unusual problem: unusual because, I suppose, most people do not try and cross-build on architectures other than x86(-64). When performing the initial L4Re build directory initialisation step... make B=mybuild ...BUILD_ARCH seems to be set to x86 even on other architectures. This then causes CCXX_FLAGS to be populated with x86-dependent settings such as -m32, and the gcc host compilers for MIPS raise errors upon encountering these unrecognised arguments. Here is the offending command in the top-level Makefile (line 376 in my version, r83 in Subversion): GENDEP_OUTPUT=$$X.out $(CC) $(CCXX_FLAGS) -c $$X -o $$X.o Although it seemed like the config step could be performed after ignoring these errors, I did wonder if there might be some undesirable consequences. In the end, I found that the following invocation was needed: make B=mybuild CC=gcc CXX=g++ LD=ld BUILD_ARCH=mips CPU=32r2 CPU_ABI=32 After that, things seem to work as expected. I imagine that there is a "chicken and egg" situation here: the appropriate settings would be obtained from the configuration, but the command being run sets up the configuration. Has anyone else seen this problem before? Paul

2 1

Fwd: l4linux running lmbench
by yangzeng 29 May '19

29 May '19

Dear Developers: I am a newcomer to l4linux, I use the default configuration to run l4linux-mag, now I want to run lmbench on l4linux, how should I put lmbench into l4linux Best Regards

2 1

L4linux startup problem
by yangzeng 20 May '19

20 May '19

Hi L4 hackers, I encountered some problems when running l4linux. I used the default configuration to run l4linux. It is good to use make qemu, but when I use make grub2iso to generate iso, use qemu-system-x86_64 -cdrom l4linux-mag.iso to run. The following error occurred mag | Hello from MAG mag | mapped frame buffer at 0x1200000 mag | ERROR: could not start screen driver for given video mode. mag | Maybe unsupported pixel format... exiting mag | MAG: destroy FB svc Ned[lua]: Warning: Capability 433000 does not support the meta protocol: -2004 lua error: rom/l4lx-gfx.cfg:52: attempt to call a nil value (method 'create'). qemu-system-x86_64: terminating on signal 2 what should i do? thanks

1 0

L4Linux with L4Re and Fiasco.OC-UX
by Paul Boddie 04 Apr '19

04 Apr '19

Hello, I have been looking at trying out L4Linux in UX mode as a first step towards its use on "native" Fiasco, and I seem to be experiencing a problem with launching the Linux kernel itself. I have followed the instructions from these pages: https://l4linux.org/download.shtml https://l4linux.org/build.shtml https://l4linux.org/use.shtml Specifically, I have an existing build of UX that has been used for some time to develop software. I have updated it to revision 83 and have checked out the l4linux_requirements, which appear to be some packages (rtc and shmc) I already have. I then performed a build once again: make O=mybuild The L4Linux repository has also been checked out and updated to revision 83. The code has been configured and built using the following invocations: make O=mybuild x86_32-ux_defconfig make O=mybuild menuconfig # to set the L4Re build directory make O=mybuild Here, the mybuild directory is distinct from the L4Re mybuild directory. For the initial RAM filesystem, I downloaded the ramdisk-x86.rd file, and I run the system as follows: make O=mybuild ux E=L4Linux-basic After the usual familiar start-up messages, I see this output specific to the configuration being launched: ---- Ned: loading file: 'rom/l4lx.cfg' libio: Warning: Query of 'vbus' failed! PH 0 offs=00001000 flags=r-x PH-type=0x1 virt=00100000 evirt=0053f000 phys=00100000 ephys=0053f000 f_sz=0043f000 memsz=0043f000 PH 1 offs=00440000 flags=rw- PH-type=0x1 virt=0053f000 evirt=00a58000 phys=0053f000 ephys=00a58000 f_sz=0006ce9f memsz=00519000 PH 2 offs=00371ee0 flags=--- PH-type=0x4 virt=00470ee0 evirt=00470f1c phys=00470ee0 ephys=00470f1c f_sz=0000003c memsz=0000003c Starting binary at 0x100000, argc=6 argv=0xafff4f84 *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa8000bd0 L4Re: rom/vmlinuz: Unhandled exception: PC=0x46980b PFA=97d47fe0 LdrFlgs=0 ---- In order to try and identify the problem, I used the following command: addr2line -e ~/L4/L4Linux/l4linux/mybuild/vmlinux 0x46980b This seems to indicate that the point of failure is at line 2727 in arch/l4/kernel/main.c which is the start of this function: int __ref L4_CV main(int argc, char **argv) So, I wonder what the problem might be that leads to a crash as the main function is being invoked. Have I missed anything obvious? All of this is being done in a Debian unstable chroot on x86. Paul

2 2