at 22:52:01 +, Richard Clark wrote:
> Adam,
>
> What's the recommended Debian distro to build on?
> Could you point me at an iso image so I can spin up a VM, please?
>
>
> Thanks!
>
> Richard
>
> ____
> From: Adam Lackorzynski
&
own type name ‘GElf_Sym’
>54 | GElf_Sym sym;
> | ^~~~
> /home/webadmin/Fiasco/l4re-snapshot-23.10.1/src/l4linux/tools/objtool/include/objtool/elf.h:82:9:
> error: unknown type name ‘Elf’
>82 | Elf *elf;
> | ^~~
>
>
>
Hi Richard,
which Linux variant are you doing this on, out of curiosity? This is
typically assembled on stable Debian, so it's good to know the
difference.
On another note, regarding virtualization, please focus on uvmm instead
of L4Linux. L4Linux is pure paravirtualization while on today's
Hi Paul,
stack size is set to 16 pages per default (64bit archs).
One can change the stack size by placing the following statement in a
program:
#include
L4RE_ELF_AUX_ELEM_T(l4re_elf_aux_mword_t, _stack_size,
L4RE_ELF_AUX_T_STACK_SIZE, 0x8);
Adam
On Mon Nov 13, 2023
Hi,
On Tue Aug 22, 2023 at 12:39:23 +0200, Radu Aron wrote:
> Is it possible to have a Windows guest OS running on top of L4Re? If so,
> could you provide some insight into how that could work? It seems like uvmm
> doesn't allow booting from an ISO image, or am I missing something?
As of today
Hi Michael,
On Mon Jun 05, 2023 at 18:39:25 +0200, Michael Willig wrote:
> I would like to try Fiasco/L4Re for a Mixed-Critical Xilinx UltraScale+
> FPGA-MPSoC (the hardware accelerators on the FPGA should be
> virtualized/isolated for mixed-critical applications) Is there somewhere an
> example
Hi Paul,
On Sat May 20, 2023 at 00:35:37 +0200, Paul Boddie wrote:
> On Friday, 19 May 2023 19:03:36 CEST Paul Boddie wrote:
> >
> > I suppose, then, the conclusion is that the CI20 UART code got inadvertently
> > broken when that functionality was reworked. Whether the UART
> > initialisation
On Fri Mar 10, 2023 at 16:56:43 +0100, lieutenant_bea...@web.de wrote:
> ok thanks
> but I still have a Linker-Error:
>
> ld: i386:x86-64 architecture of input file
> `/usr/lib/gcc/x86_64-linux-gnu/9/crtbeginS.o' is incompatible with i386 output
> ld: i386:x86-64 architecture of input file
>
en I load the uimage into this address, I unfortunately get the same error
> message.
> Is there any other advice?
> Thank you
>
> Von: l4-hackers im Auftrag von Adam
> Lackorzynski
> Gesendet: Donnerstag, September 1, 2022 12:04 AM
> An
Hi,
On Wed Aug 31, 2022 at 08:01:05 +, rib0327 wrote:
> I am currently trying to get the L4Re running on the NXP LX2160 with U-Boot.
> When I try to load a .uimage I get the following error message:
> FDT and ATAGS support not compiled in
I believe this happens because u-boot needs the
Hi Paul,
On Sun Aug 21, 2022 at 00:18:57 +0200, Paul Boddie wrote:
> On Monday, 18 April 2022 23:26:03 CEST Adam Lackorzynski wrote:
> >
> > On Tue Apr 12, 2022 at 01:09:40 +0200, Paul Boddie wrote:
> > >
> > > This might just sound like me complaining, but I al
Hi,
Thanks for the elaborate description. Please use
SRC_C = src/main.c
in the Makefile for the time being.
Adam
On Thu Aug 25, 2022 at 09:40:54 +, rib0327 wrote:
> Hello everyone,
>
>
>
> We have a question regarding the newest Kernel version available on Git
> (current date:
Hi Paul,
On Fri Apr 29, 2022 at 00:28:10 +0200, Paul Boddie wrote:
> On Thursday, 28 April 2022 23:21:46 CEST Adam Lackorzynski wrote:
> >
> > On Mon Apr 25, 2022 at 17:55:45 +0200, Paul Boddie wrote:
> > >
> > > I didn't really understand this when
Hi Paul,
On Mon Apr 25, 2022 at 17:55:45 +0200, Paul Boddie wrote:
> On Monday, 25 April 2022 01:04:44 CEST Adam Lackorzynski wrote:
> >
> > Thanks for the example.
>
> Thanks for looking at it! I appreciate the help.
>
> > I believe I see the issue
On Sat Apr 23, 2022 at 00:40:05 +0200, Paul Boddie wrote:
> On Friday, 22 April 2022 01:16:44 CEST Paul Boddie wrote:
> >
> > On Thursday, 21 April 2022 22:57:40 CEST Adam Lackorzynski wrote:
> > >
> > > Maybe it helps to share some code here?
> >
>
Hi Paul,
On Tue Apr 19, 2022 at 01:20:30 +0200, Paul Boddie wrote:
> On Monday, 18 April 2022 23:26:03 CEST you wrote:
> > Hi Paul,
> >
> > On Tue Apr 12, 2022 at 01:09:40 +0200, Paul Boddie wrote:
> > >
> > > OK, I did see that function being used, too, but I also found plenty of
> > > other
Hi,
sorry, this should be fixed now in the latest snapshot.
Adam
On Mon Mar 21, 2022 at 00:13:12 +0800, Haohui Mai wrote:
> Sorry I forgot to mention that I'm on Ubuntu 20.04 and trying to run
> the x86_64 port of L4Linux.
>
> ~Haohui
>
> On Sun, Mar 20, 2022 at 10:38 PM Haohui Mai wrote:
>
Hi Paul,
On Tue Apr 12, 2022 at 01:09:40 +0200, Paul Boddie wrote:
> On Monday, 11 April 2022 01:02:37 CEST Adam Lackorzynski wrote:
> > Hi Paul,
> >
> > On Sun Apr 10, 2022 at 18:58:10 +0200, Paul Boddie wrote:
> > > I finally got round to experimenting with
Hi Paul,
On Sun Apr 10, 2022 at 18:58:10 +0200, Paul Boddie wrote:
> I finally got round to experimenting with L4Re again, but in attempting to
> investigate task creation, I seem to have some difficulties understanding the
> mechanism by which tasks are typically created and how the
Hi,
On Fri Feb 04, 2022 at 04:34:44 -0500, Ashwin Krishnakumar wrote:
> Hello all,
> I have created this issue in the manifest repo.
> Issue : https://github.com/kernkonzept/manifest/issues/12
>
> I am writing it again.
Thanks Ashwin. Please bear with us while we work through it.
> I am trying
On Sun Sep 19, 2021 at 09:51:07 +0200, Matthieu Fatrez wrote:
> Sorry, answer to myself. I miss the BLK_DEV_RAM=y param in kernel
> compilation to have access to /dev/ram0.
Yep, that's right.
> Looking now for the mmc access.
I'm afraid but it won't work with the single device tree node.
Hi Martin,
On Fri Sep 17, 2021 at 13:05:38 +, Martin Decky wrote:
> Dear L4 hackers,
>
> I have implemented a basic support for the HiKey960 board (based on the
> Kirin 960 SoC) [1] in Fiasco.OC and L4Re. If you are interested, please feel
> free to examine the code at GitHub [2]. I would be
Hi,
On Thu Sep 09, 2021 at 16:01:18 +0200, Matthieu Fatrez wrote:
> Thanks Adam. I will try to use uvmm.
>
> Do you plan to have the 64bit/rpi4 ready? And when if planned.
It is so far that VMs run, e.g., the VM examples will also run on the
rpi4.
Adam
> > Le 9 sept. 202
Hi Matthieu,
On Mon Sep 06, 2021 at 22:35:25 +0200, Matthieu Fatrez wrote:
> I tried to use l4re hypervisor on raspberry pi 4. Prebuild image works but
> not for my needs.
> In fact, I want to use l4re running on raspberry pi 4 (aarch64) with 1 or
> more tasks (such hello, ...) and 1 linux 64
Hi Paul,
On Sat Jun 19, 2021 at 02:00:18 +0200, Paul Boddie wrote:
> On Monday, 14 June 2021 22:21:50 CEST Adam Lackorzynski wrote:
> >
> > On Mon Jun 14, 2021 at 13:15:22 +0200, Yanneck Geiger wrote:
> > > Hello, unfortunately I can't get L4Re running on the Raspber
Hi Yanneck,
On Mon Jun 14, 2021 at 13:15:22 +0200, Yanneck Geiger wrote:
> Hello, unfortunately I can't get L4Re running on the Raspberry Pi 3 / 3+
> using the provided Guider (https://l4re.org/rpi.html). I did the 64-Bit
> setup accordingly with the provided U-Boot and the ready-to-use images.
>
Hi,
On Sun Apr 04, 2021 at 12:51:25 +0200, John Galt wrote:
> Is it possible to share resources between two VMs running Linux?
> After defining the io_bus and the io configuration, just one VM is getting
> access to the resource while the other displays:
> ERROR: binding irq 34, result is -1
Hi,
Please use -m 2048 for QEMU as the virtual platform is using 2GB.
Adam
On Thu Apr 01, 2021 at 22:02:28 +, Jorge Miguel Perez Utrera wrote:
> Hi,
>
> I am trying to build the first tutorial, but cross-compiling for the Zynq
> Ultrascale+. However, when I run "make E=hello qemu" I get
On Thu Jan 14, 2021 at 23:54:38 +0100, Matthias Lange wrote:
> On [14-01-2021 23:24], Andreas Resch wrote:
> > Hello everyone,
> >
> > as part of a practical course at my university my group has to bring
> > Fiasco.OC and L4re to the NanoPC-T3 Plus which is powered by the S5P6818
> > from
Hi Andreas,
On Mon Dec 14, 2020 at 15:35:08 -0800, Andreas Steinmetzler wrote:
> in some experiments I'm trying to run Fiasco/L4re on a Aaeon FWS2360
> (https://www.aaeon.com/en/p/desktop-network-appliance-fws-2360) with an
> Intel Atom C3558. Unfortunately Fiasco gets stuck on boot when trying
Hi Mohamed,
on the rpi4 there's a global offset used in Linux's device tree (check
for ranges statement in bcm2711.dtsi). The address of the sdhc/mmc
controller rather is 0xfe30. Also use 0x7e + 32 for the IRQ to
consider it's an SPI.
Adam
On Wed Oct 07, 2020 at 20:28:44 +0200, Mohamed
Hi,
On Mon Aug 17, 2020 at 22:35:11 -0700, Andreas Steinmetzler wrote:
> Hi,
>
> I'm experimenting with the TuD Snapshot release 2020.07.1 and can compile
> and run Fiasco, L4re and L4Linux in their basic configurations (amd64
> architecture) using the default l4lx.cfg file of the distribution.
Hi,
On Wed Jul 15, 2020 at 20:49:14 -0700, Andreas Steinmetzler wrote:
> I followed the tutorials on github to get a basic L4re environment compiled
> and running (Hello World) on a embedded x86 board (more specifically APU2
> https://www.pcengines.ch/apu2.htm). Everything worked fine - really
Hi,
this setting is only relevant for bootstrap. The kernel has its own
(configurable) alignment checking setting.
For bootstrap it is merely a historic precaution thing and with today's
compilers / CPUs it should be removed, at least for v6+.
Adam
On Mon Nov 25, 2019 at 15:03:37 +, Al
Hi,
the case for cmpxchg64 is currently not handled, that's why it faults.
Could you make me available the go program or at least the code around
the call to __kuser_cmpxchg64?
Adam
On Wed Nov 13, 2019 at 08:45:22 +0530, Sateesh K wrote:
> Hi,
> My setup is as follows:
> l4linux 4.19.0-l4
Hi Paul,
On Fri Aug 30, 2019 at 13:43:10 +0200, Paul Boddie wrote:
> On Thursday 29. August 2019 12.31.49 Paul Boddie wrote:
> > On Wednesday 28. August 2019 16.47.31 Sarah Hoffmann wrote:
> > > On 8/28/19 4:07 PM, Paul Boddie wrote:
> > > > make O=mybuild qemu E=hello QEMU_OPTIONS='-nographic -M
On Thu Aug 29, 2019 at 23:06:40 +0200, clim atisefr wrote:
> I know the Raspberry PI 3 does not support the full virtualization and only
> para-virtualization is supported.
> It seems that the Raspberry PI 4 with the Broadcom 2711 (Quad-core
> Cortex-A72 ARM v8 64-bit SoC @ 1.5 GHz) may support
Hi Paul,
UX is an interesting way of virtualizing a kernel and gives interesting
insights into both Fiasco and Linux. I guess with some work it would be
well possible to make this work on MIPS.
But, before going on this endeavor what about QEMU? It should be much
quicker and simpler to run it
ew named NIC device
>
> NIC = Hw.Device(function()
>
> Property.hid = "smsc9514";
>
> compatible = {"usb424,ec00"};
>
> -- Resource.regs = Res.mmio(0x4e00, 0x4e000fff);
__
> From: Lei Zhou
> Sent: Thursday, June 13, 2019 12:24 PM
> To: Adam Lackorzynski; l4-hackers@os.inf.tu-dresden.de
> Subject: RE: How to enable Guest Linux VM on Raspberry PI3?
>
> Thanks Adam, much appreciated!by enabling the FPU fixes the exception.
>
Hi,
On Thu Jun 13, 2019 at 19:36:33 +0200, Paul Boddie wrote:
> On Thursday 13. June 2019 17.48.59 Adam Lackorzynski wrote:
> > On Wed Jun 12, 2019 at 00:34:02 +0200, Paul Boddie wrote:
> > >
> > > Perhaps take a look at the following:
> > >
>
On Wed Jun 12, 2019 at 00:34:02 +0200, Paul Boddie wrote:
> On Tuesday 11. June 2019 23.32.43 Adam Lackorzynski wrote:
> > On Tue Jun 11, 2019 at 02:00:00 +0200, Paul Boddie wrote:
> > > Unfortunately, nothing more is shown and there is no register dump. Maybe
> > >
*/
>
> lua_pop(L, 1); /* pop global table */
>
> return 1; /* return 'package' table */
>
> }
>
> Any hints would b
On Tue Jun 11, 2019 at 02:00:00 +0200, Paul Boddie wrote:
> On Tuesday 11. June 2019 00.18.43 Paul Boddie wrote:
> > On Tuesday 11. June 2019 00.08.59 Adam Lackorzynski wrote:
> > > If it just reboots in the middle of a rather normal C function, then
> > > it's likel
On Mon Jun 10, 2019 at 20:16:55 +0200, Paul Boddie wrote:
> On Wednesday 29. May 2019 18.27.03 Paul Boddie wrote:
> >
> > P.S. I have a selfish interest in following this as I could imagine also
> > trying out L4Re on the Raspberry Pi at some point. I guess that the
> > framebuffer isn't
Hi Paul,
On Mon Jun 10, 2019 at 16:50:57 +0200, Paul Boddie wrote:
> 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).
>
On Fri Jun 07, 2019 at 18:27:18 +, Lei Zhou wrote:
> 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
Hi,
you need to have the mkimage tool available, which is typically
available through the u-boot-tools package (or similar).
For the other error, please disable Virtualization support in the Fiasco
configuration. The raspberry pi does not support hardware-assisted
virtualization.
Adam
On Wed
On Tue May 28, 2019 at 21:21:41 +, Lei Zhou wrote:
> Thanks Paul for your prompt response. I will give it try and see how it
> goes.Regards, Lei
One missing piece is probably that u-boot should be put on the rpi to
load the bootstrap.uimage.
Adam
On Wed May 29, 2019 at 17:11:19 +0800, yangzeng wrote:
> 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
I guess you're using a ramdisk right now, so you can add
Hi Paul,
On Thu Mar 28, 2019 at 23:28:17 +0100, Paul Boddie wrote:
> 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
Hi,
On Wed Mar 27, 2019 at 14:07:42 +0100, Dejan Cotra wrote:
> Im trying to run L4Linux on Raspberry Pi 3B.
> So far I was able to build Fiasco kernel and L4Re for Raspberry Pi 3B.
> I used aarch64-linux-gnu-gcc toolchain.
>
> Also I was able to create Uboot image for hello config, which I
>
Hi,
On Tue Feb 26, 2019 at 10:06:20 +0800, Xinyue Wu wrote:
> I have been trying to mount ssd and hard disk in l4linux. There are some
> similiar questions in previous archives, and I have done the following
> things according to them:
>
>- configure 'devs' file and 'io' file, add sata to
Hi,
On Wed Feb 20, 2019 at 09:44:35 +, yadong.li wrote:
> I am studying how to support emmc storage in L4Re.
>I have read the file l4linux/drivers/block/l4bd.c.
>I have some questions
>
> 1¡¢ In ¡°l4linux/drivers/block/l4bd.c¡±, I can¡¯t find the function
> implementation of
Hi,
On Wed Feb 13, 2019 at 15:25:53 +0100, Canberk Demirsoy wrote:
> I have a simple question regarding the communication of L4Linux and L4re. I
> have already read previous entries but could not solve my problem.
>
> I am able to establish a communication between the tasks in L4re, but what
> I
Hi,
On Tue Sep 18, 2018 at 22:45:41 +0100, Yuxuan Shui wrote:
> In cpu-64.cpp, in function Cpu::setup_sysenter, Fiasco try to set
> IA32_FMASK (called MSR_SFMASK in the code) to ~0ULL. However, only the
> lower 32bit of FMASK should be written to.
>
> This cause problems on some platforms.
On Fri Aug 03, 2018 at 15:49:56 +0200, Paul Boddie wrote:
> On Friday 3. August 2018 15.36.50 Adam Lackorzynski wrote:
> >
> > On Fri Aug 03, 2018 at 00:26:45 +0200, Paul Boddie wrote:
> > >
> > > I know that the ldscripts have been changed, but I struggle t
Hi Paul,
On Fri Aug 03, 2018 at 00:26:45 +0200, Paul Boddie wrote:
> I thought I'd try and get L4Re and the UX variant of Fiasco.OC working again.
> Various errors with the actual compiler - not typical compilation errors -
> have previously occurred, but system updates come along every so
Hi,
On Thu May 24, 2018 at 14:05:57 +, 李 鼎基 wrote:
> I’ve been trying to find or write a webserver directly on L4Re (*NO* L4Linux
> involved) based on snapshot “l4re-snapshot-17.12”.
> At first, I noticed that there was already a web server in
> “l4re-snapshot-17.12/src/l4/pkg/ankh”.
> But
On Sun May 20, 2018 at 00:47:02 +0200, Paul Boddie wrote:
> On Monday 14. May 2018 21.18.04 Adam Lackorzynski wrote:
> >
> > You can set LD_DEBUG=1 in the environment of your program to make the
> > dynamic loader tell you something. LD_TRACE_LOADED_OBJECTS=1 might als
On Mon Apr 23, 2018 at 01:28:59 +0200, Paul Boddie wrote:
> Hello again,
>
> I have been implementing input drivers for the keypad/keyboard provided by
> the
> Ben NanoNote and Letux 400 notebook computer, and although I appear to have
> implemented something that works (tested using
Hi Paul,
On Fri May 11, 2018 at 01:00:11 +0200, Paul Boddie wrote:
> I have been busy writing libraries and programs for L4Re and recently had to
> think about the size of the payloads I have been deploying. It appears that
> in
> the build system, one can use MODE=shared to build
On Thu May 03, 2018 at 11:18:03 +0800, nico.hacker wrote:
> The previous test is not enough to cause error, this error is not related to
> peripherals, I have removed almost all peripheral driversIn the
> previous test, I added a delay operation before the vm2 start, so that vm1
> completely
es?
Adam
> On 4/9/2018 06:28ï¼ Adam Lackorzynski<a...@os.inf.tu-dresden.de> wroteï¼
>
> Hi Nico,
>
> On Fri Mar 30, 2018 at 10:15:33 +0800, nico wrote:
>
> Hi Adam, I'm using an eight-core Cortex-A53 processor. The vm is
> running 64bit Li
Hi Nico,
On Fri Mar 30, 2018 at 10:15:33 +0800, nico wrote:
> Hi Adam, I'm using an eight-core Cortex-A53 processor. The vm is
> running 64bit Linux. It is recommended to start two or three vms, that
> will be easier to reproduce this problem.
So, I tried several things but cannot reproduce this
Hi,
On Thu Mar 29, 2018 at 20:48:34 +0800, nico wrote:
> Hi l4 hackers,
>
> I recently encountered an assertion failure error during the vm linux boot
> process, the kernel error is at src/kern/arm/thread-arm-hyp.cpp.
> --
>
On Tue Mar 13, 2018 at 11:40:37 +, Jiang qihong wrote:
> The whole command , qemu–system–aarch64 -kernel uimage -M vexpress -a15 -cpu
> cortex-a57 -smp 2 -m256 --nographic
> The issue is that when running into shell, i didn't find two cpus.
> The parameter "-smp 2",didn't work.
> Does
Hi,
On Tue Mar 13, 2018 at 11:58:57 +0800, Zihan Yang wrote:
> I'm trying to debug L4Linux using jdb in Fiasco. I have added a
> breakpoint in a function(e.g, syscall_exit), and it did hit into jdb
> when I run. However, when I type 'bt' in jdb, it only prints the
> values in the stack, or worse,
Hi,
On Thu Mar 08, 2018 at 11:00:03 +0800, Zeyu Mi wrote:
> On Thu, Mar 8, 2018 at 8:14 AM, Adam Lackorzynski <a...@os.inf.tu-dresden.de
> > wrote:
>
> >
> > On Wed Mar 07, 2018 at 15:50:24 +0800, Zeyu Mi wrote:
> > > Sorry for bothering you again...
> >
On Thu Mar 08, 2018 at 00:52:55 +0100, Paul Boddie wrote:
> On Wednesday 7. March 2018 01.22.46 Paul Boddie wrote:
> >
> > Currently, I have reason to believe that an exception occurs causing the
> > sigma0 thread to terminate, but it's getting late and my debugging
> > efficiency is suffering.
On Wed Mar 07, 2018 at 15:50:24 +0800, Zeyu Mi wrote:
> Sorry for bothering you again...
>
> I have changed to snapshot-17.09 and the "s" command works normally.
>
> I also disabled the VCPU thread model in the L4Linux config and it can be
> compiled
> without any error :)
>
> However, the
Hi,
On Tue Mar 06, 2018 at 10:22:18 +0800, Zeyu Mi wrote:
> On Tue, Mar 6, 2018 at 9:20 AM, Zeyu Mi <yzmiz...@gmail.com> wrote:
>
> >
> >
> > On Tue, Mar 6, 2018 at 7:50 AM, Adam Lackorzynski <
> > a...@os.inf.tu-dresden.de> wrote:
> >
> >>
On Tue Mar 06, 2018 at 01:14:25 +0100, Paul Boddie wrote:
> On Tuesday 6. March 2018 00.46.29 Adam Lackorzynski wrote:
> >
> > All what you write sounds good. In any case the eret must restore state
> > including setting the right interrupt state. Are you getting timer
>
Hi,
On Mon Mar 05, 2018 at 19:47:19 +0800, Zeyu Mi wrote:
> I am studying the implementation of the Fiasco.OC and the L4Linux.
>
> I have searched on the Internet and many papers and documents record that
> L4Linux runs as an L4 server and
> any L4Linux user process is a new task, which has a
Hi Paul,
On Sun Mar 04, 2018 at 22:25:12 +0100, Paul Boddie wrote:
> I've been trying to coerce L4Re and Fiasco.OC to work with the Ben NanoNote,
> which is related to the MIPS Creator CI20 that is (mostly - see earlier
> discussions) supported by this software. There are a few challenges
On Wed Feb 07, 2018 at 08:02:15 +, Bob Liu wrote:
> L4Linux.org mentioned:
> "Compared to monolithic Linux, there is a small performance tradeoff because
> of the µ-kernel architecture. However, the initial L4Linux has been somewhat
> optimized, and on L4/x86 it has a very acceptable
On Fri Feb 02, 2018 at 16:45:13 +0100, Paul Boddie wrote:
> On Wednesday 10. January 2018 00.48.03 Adam Lackorzynski wrote:
> >
> > Adding the .global to the asm block makes thread2 a global symbol which
> > I'd like not to have here (contrary to L4UTIL_THREAD_FUNC). Just d
Hi,
On Fri Feb 02, 2018 at 14:32:08 +0100, Josef Stark wrote:
> when a page fault occurs, does the Instruction Register contain the actual
> instruction that caused the fault or the previous instruction? In the former
> case, how can I access it? I need the opcode + the operands (like
>
On Mon Jan 29, 2018 at 22:36:34 +0100, Paul Boddie wrote:
> More awkward news from Debian on i386! I was looking to build the "Linux
> Usermode Platform" variant of Fiasco-OC on i386 (well, Pentium 4) and
> encountered a couple of issues.
>
> Firstly, "struct ucontext" is mentioned in
On Mon Jan 29, 2018 at 23:40:15 +0100, Paul Boddie wrote:
> As promised, my other error report...
>
> With Fiasco-OC built, I concentrated on building L4Re for i386, but this led
> to me encountering this rather frustrating error:
>
> [l4util] ==> Linking to shared libl4util.so
>
Hi,
On Thu Jan 25, 2018 at 16:32:25 +, Stark, Josef wrote:
> Hey,
>
> in Fiasco.OC we have a function inside
> src/kernel/foc/l4/pkg/l4sys/include/thread.h
> > L4_INLINE l4_msgtag_t
> > l4_thread_ex_regs_ret(l4_cap_idx_t thread, l4_addr_t *ip, l4_addr_t *sp,
> >
On Thu Jan 18, 2018 at 08:47:52 +0300, Valery V. Sedletski wrote:
> On 18.01.2018 02:41, Adam Lackorzynski wrote:
> > On Tue Jan 16, 2018 at 01:38:18 +0300, Valery V. Sedletski wrote:
> > > On 29.12.2017 01:27, Adam Lackorzynski wrote:
> > > > On Thu Dec 28, 20
On Tue Jan 16, 2018 at 01:38:18 +0300, Valery V. Sedletski wrote:
> On 29.12.2017 01:27, Adam Lackorzynski wrote:
> > On Thu Dec 28, 2017 at 05:59:05 +0300, Valery V. Sedletski wrote:
> > > On 28.12.2017 03:22, Adam Lackorzynski wrote:
> > > > On Thu Dec 28, 20
ed in your modules.list entry.
Does this help?
Adam
> On 1/10/2018 16:40ï¼ Matthias Lange<matthias.la...@kernkonzept.com> wroteï¼
>
> Hi Nico,
>
> On 2018-0110 at 09:11:09 +0800, nico.hacker wrote:
> > Yes, that's it. Do you have any good suggesti
On Tue Jan 09, 2018 at 23:17:10 +0100, Paul Boddie wrote:
> On Tuesday 9. January 2018 01.02.58 Paul Boddie wrote:
> >
> > So, I am assuming that the compiler gets confused by the freestanding
> > assembly language definition of the function, and the object goes missing
> > in some way that then
Hi nico,
On Tue Jan 09, 2018 at 19:18:20 +0800, nico wrote:
> I started uvmm and found that all ram space allocated to vm are cleared.
Yes, sure. We do not want to see any other data in there, possibly
coming from another domain and leaking some information.
> But I do not need to do that,
On Mon Jan 08, 2018 at 01:14:09 +0100, Paul Boddie wrote:
> On Monday 8. January 2018 00.37.41 Adam Lackorzynski wrote:
> >
> > Is it ok if you have visibility("hidden") instead of internal?
>
> No, it would seem that all other visibility types produce the same er
Hi Paul,
On Sun Jan 07, 2018 at 14:15:13 +0100, Paul Boddie wrote:
> Sorry to follow up on myself again...
>
> On Thursday 21. December 2017 01.55.51 Paul Boddie wrote:
> > On Wednesday 20. December 2017 16.52.45 Paul Boddie wrote:
> > > However, another problem has emerged when trying to build
On Thu Dec 28, 2017 at 05:59:05 +0300, Valery V. Sedletski wrote:
> On 28.12.2017 03:22, Adam Lackorzynski wrote:
> > On Thu Dec 28, 2017 at 02:54:20 +0300, Valery V. Sedletski wrote:
> > > On 28.12.2017 02:29, Adam Lackorzynski wrote:
> > > > On Wed Dec 27, 20
On Thu Dec 28, 2017 at 02:54:20 +0300, Valery V. Sedletski wrote:
> On 28.12.2017 02:29, Adam Lackorzynski wrote:
> > On Wed Dec 27, 2017 at 18:33:16 +0300, Valery V. Sedletski wrote:
> > > On 27.12.2017 13:05, Matthias Lange wrote:
> > > > Hi Valery,
> > >
On Wed Dec 27, 2017 at 18:33:16 +0300, Valery V. Sedletski wrote:
> On 27.12.2017 13:05, Matthias Lange wrote:
> > Hi Valery,
> >
> > > On 26. Dec 2017, at 17:54, Valery V. Sedletski <_valer...@mail.ru> wrote:
> > >
> > > Hi. I'm trying to debug my program with jdb. (I'm using the old L4/Fiasco
Hi,
On Fri Dec 15, 2017 at 15:09:54 +0530, vmc doe wrote:
> I tried to build l4+l4Re+l4linux for raspberry pi 2.
> The build was successful, but when I tried to run this in qemu I am getting
> the following error.
> Could you pls help me to fix this error?
> I am new to L4 and L4Re and would
Hi,
On Fri Dec 15, 2017 at 12:09:43 +, Sathish Kumar Balasubramaniam -ERS, HCL
Tech wrote:
> Build machine is Debian 8.10 (jessie) 64-Bit
> GCC toolchain is gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf
> I tried to build the l4re-snapshot-17.10 for Freescale iMX6 and the build
>
at the problem is.
Thanks, Adam
> [0] https://github.com/raspberrypi/firmware/tree/1.20170811/boot
>
> On 24.11.2017 01:10, Adam Lackorzynski wrote:
> > Hi,
> >
> > On Tue Nov 21, 2017 at 16:19:52 +0100, Alexander Weidinger wrote:
> >> Hello Antoine, hello l4-hacker
Hi,
On Tue Nov 21, 2017 at 16:19:52 +0100, Alexander Weidinger wrote:
> Hello Antoine, hello l4-hackers,
>
> I'm currently trying to replicate the port to RPi2 for Fiasco/Genode,
> which works great, until I get stuck in the boot process:
>
> > L4 Bootstrapper
On Wed Nov 01, 2017 at 11:17:12 +0800, Leslie Zhai wrote:
> still failed:
>
> QEMU-cmd: qemu-system-arm -kernel
> /data/project/xiangzhai/l4re/l4/build-arm/images/bootstrap.elf -serial stdio
> -M integratorcp -cpu arm926 -m 256
>
> I am trying to build Fiaso and L4Re with different GNU
On Wed Nov 01, 2017 at 01:03:36 +0100, Paul Boddie wrote:
> On Wednesday 1. November 2017 00.38.23 Adam Lackorzynski wrote:
> >
>
> [Cache detail querying]
>
> > I just modified the code to have a fixed value and that worked for me as
> > a quick hack. I don't th
Hi,
On Mon Oct 30, 2017 at 18:38:40 +0100, Paul Boddie wrote:
> > > to do some assembly language programming here just to recover from the
> > > exception. In this case, however, the emulated instruction is very
> > > simple, although I did take the liberty of rearranging the emulation
> > >
Hi,
On Mon Oct 23, 2017 at 01:50:47 +0200, Paul Boddie wrote:
> A quick reply as it is rather late...
So often :)
> On Monday 23. October 2017 00.55.53 Adam Lackorzynski wrote:
> > On Mon Oct 16, 2017 at 15:35:22 +0200, Paul Boddie wrote:
> > > On Monday 16. Octob
On Sat Oct 14, 2017 at 17:09:46 +0200, Paul Boddie wrote:
> On Wednesday 11. October 2017 15.33.58 Manolis Ragkousis wrote:
> >
> > Finally I have a question, Are you accepting patches for L4 and L4Linux?
> > I could make my git patches more presentable and send them here if you
> > want, to be
1 - 100 of 1472 matches
Mail list logo
