Re: Questions about Fiasco.OC scheduler and L4Linux

On Fri Mar 31, 2017 at 08:07:00 +, Marc CHALAND wrote: > Le jeu. 30 mars 2017 à 23:54, Adam Lackorzynski > a écrit : > > > > > > a7 hangs exactly at that > > > point. Any idea to fix this ? > > > > Multiple. You need to make sure that u-boot boots you non-secure >

Re: Questions about Fiasco.OC scheduler and L4Linux

Le jeu. 30 mars 2017 à 23:54, Adam Lackorzynski a écrit : > > > a7 hangs exactly at that > > point. Any idea to fix this ? > > Multiple. You need to make sure that u-boot boots you non-secure > (there's no hyp-mode on the secure side). u-boot needs to be enabled for >

Re: Questions about Fiasco.OC scheduler and L4Linux

On Thu Mar 30, 2017 at 14:42:36 +, Marc CHALAND wrote: > I did some tests and I'm stuck on bootstrap. I assume that omap (a15) and > imx7 (a7) have the same switch_to_hyp mechanism. No, they haven't. Those switching routines are there to switch from a lower-priv level to a higher one, i.e.

Re: Questions about Fiasco.OC scheduler and L4Linux

Le lun. 27 mars 2017 à 15:59, Christian Ludwig a écrit : I guess the question was more about running umodified Linux in a VM on top of Fiasco. In this scenario, Fiasco acts as the hypervisor only. There is the 'uvmm' package that implements a virtual machine monitor,

Re: Questions about Fiasco.OC scheduler and L4Linux

Le lun. 27 mars 2017 à 15:59, Christian Ludwig a écrit : Hi, On Monday, 27. March 2017, 15:24:59 Matthias Lange wrote: > On 03/27/2017 03:12 PM, Marc CHALAND wrote: > > > a écrit : > > With a i.MX7d you

Re: Questions about Fiasco.OC scheduler and L4Linux

Hi, On Monday, 27. March 2017, 15:24:59 Matthias Lange wrote: > On 03/27/2017 03:12 PM, Marc CHALAND wrote: > > > a écrit : > > With a i.MX7d you have hardware support for virtualization, so what > > about using that, i.e.

Re: Questions about Fiasco.OC scheduler and L4Linux

Hi, On 03/27/2017 03:12 PM, Marc CHALAND wrote: > Hi > > Le mer. 22 mars 2017 à 00:59, Adam Lackorzynski > > a écrit : > > > With a i.MX7d you have hardware support for virtualization, so what > about using that, i.e. running

Re: Questions about Fiasco.OC scheduler and L4Linux

Hi Le mer. 22 mars 2017 à 00:59, Adam Lackorzynski a écrit : > > With a i.MX7d you have hardware support for virtualization, so what > about using that, i.e. running normal Linux in a VM? Getting an L4Linux > for an older version is of course possible but a bit of

Re: Questions about Fiasco.OC scheduler and L4Linux

Hi, On Fri Mar 24, 2017 at 22:48:03 +0100, Marc CHALAND wrote: > 2017-03-22 23:45 GMT+01:00 Adam Lackorzynski : > > Basically the vCPU model is an asynchronous execution model, that is > > very similar to an actual CPU. I.e. you have vCPU that executes code and > > that

Re: Questions about Fiasco.OC scheduler and L4Linux

Le mer. 22 mars 2017 à 00:59, Adam Lackorzynski a écrit : On Tue Mar 21, 2017 at 08:31:06 +0100, Marc CHALAND wrote: > I'm doing a study to port old software on top of Fiasco.OC. This soft uses > routines which blocks thread scheduling between EnterRegion and

Re: Questions about Fiasco.OC scheduler and L4Linux

Hey Marc, On Tue Mar 21, 2017 at 08:31:06 +0100, Marc CHALAND wrote: > I'm doing a study to port old software on top of Fiasco.OC. This soft uses > routines which blocks thread scheduling between EnterRegion and LeaveRegion > call. Is there any equivalent on TUDOS ? Did somebody already get this

Questions about Fiasco.OC scheduler and L4Linux

Hi, I'm doing a study to port old software on top of Fiasco.OC. This soft uses routines which blocks thread scheduling between EnterRegion and LeaveRegion call. Is there any equivalent on TUDOS ? Did somebody already get this challenge ? I would like to know if L4Linux uses Fiasco.OC scheduler or