Re: loading a simple hypervisor(just prints Hello World) before the linux kernel

>Hint: Just branching to El1 probably isn't enough. >Documentation/arm64/booting.rst All these conditions should be set by the bootloader when it loads the hypervisor(which prints Hello World at first). I only have to keep the dtb address in x0 and jump to EL! I have also added the kernel image

Re: loading a simple hypervisor(just prints Hello World) before the linux kernel

On Wed, 10 Nov 2021 23:38:11 +0500, Mushahid Hussain said: > I have successfully done so. I can see the Hello World printed to UART by > two different binaries. What I cannot do is to jump from a binary(let's > call it a simple hypervisor, which prints Hello World) at EL2 to the > standard linux

loading a simple hypervisor(just prints Hello World) before the linux kernel

Hi, I'm trying to learn about the Linux kernel and the bare metal world on raspberry pi 4. After writing a simple kernel, which would print Hello World to UART, I tried to write Hello World using two different binaries loaded at two different addresses(and on two different exception levels!(EL2

Re: correct source tree to make contributions to Linux thermal framework

On Tue, Nov 09, 2021 at 08:15:46PM +, Balakrishnan, Anand wrote: > Hello Developers, > > > At our company, we maintain an internal thermal framework patch. We are > exploring the option to up-stream this patch so we don't have to keep porting > this from one Kernel version to the other. >

Will two processes each holding a given spin lock be seen as ordered by a third process not holding that lock?

Hi all, In tools/memory-model, there are two litmus tests named *ISA2+pooncelock+pooncelock+pombonce *and *Z6.0+pooncelock+pooncelock+pombonce. *As far as I understand it, these two files test exactly the same thing: will two processes each holding a given spin lock be seen as ordered by a third