Re: arm: handle hypervisor mode

2016-01-23 Thread Patrick Wildt
On Sun, Jan 24, 2016 at 03:02:29AM +1100, Jonathan Gray wrote: > On Sat, Jan 23, 2016 at 02:54:58PM +0100, Patrick Wildt wrote: > > On Sun, Jan 24, 2016 at 12:33:42AM +1100, Jonathan Gray wrote: > > > On Fri, Jan 22, 2016 at 09:36:49PM +0100, Patrick Wildt wrote: > > > > Hi, > > > > > > > > the hy

Re: arm: handle hypervisor mode

2016-01-23 Thread Jonathan Gray
On Sat, Jan 23, 2016 at 02:54:58PM +0100, Patrick Wildt wrote: > On Sun, Jan 24, 2016 at 12:33:42AM +1100, Jonathan Gray wrote: > > On Fri, Jan 22, 2016 at 09:36:49PM +0100, Patrick Wildt wrote: > > > Hi, > > > > > > the hypervisor mode, which virtualization-enabled boards might boot in, > > > is

Re: arm: handle hypervisor mode

2016-01-23 Thread Patrick Wildt
On Sun, Jan 24, 2016 at 12:33:42AM +1100, Jonathan Gray wrote: > On Fri, Jan 22, 2016 at 09:36:49PM +0100, Patrick Wildt wrote: > > Hi, > > > > the hypervisor mode, which virtualization-enabled boards might boot in, > > is basically a privilege level above the usual SVC mode the kernel is > > runn

Re: arm: handle hypervisor mode

2016-01-23 Thread Jonathan Gray
On Fri, Jan 22, 2016 at 09:36:49PM +0100, Patrick Wildt wrote: > Hi, > > the hypervisor mode, which virtualization-enabled boards might boot in, > is basically a privilege level above the usual SVC mode the kernel is > running in. It does not support the full instruction set and we, as > a "guest

arm: handle hypervisor mode

2016-01-22 Thread Patrick Wildt
Hi, the hypervisor mode, which virtualization-enabled boards might boot in, is basically a privilege level above the usual SVC mode the kernel is running in. It does not support the full instruction set and we, as a "guest" OS, need to step down and run in SVC. Otherwise we crash really early on