On 06/28/2013 05:51 AM, Masahiro Yamada wrote:
Hi Andre
[RFC]
I'd like to suggest to separate HYP-switching code
from Non-secure switching.
Thanks for stepping up and providing a use-case!
The first version of the patches had those two separate cases, but I
later merged them in favor of read
Hi Andre
[RFC]
I'd like to suggest to separate HYP-switching code
from Non-secure switching.
And define different macros, for example:
CONFIG_ARMV7_NONSECURE : switch to nonsecure
CONFIG_ARMV7_VIRT : switch to hypervisor
Of cource, CONFIG_ARMV7_NONSECURE must be defined
when using CONFI
On 06/21/2013 04:38 PM, Nikolay Nikolaev wrote:
Hello,
On Thu, Jun 13, 2013 at 2:01 PM, Andre Przywara
mailto:andre.przyw...@linaro.org>> wrote:
For the KVM and XEN hypervisors to be usable, we need to enter the
kernel in HYP mode. Now that we already are in non-secure state,
HYP m
Hello,
On Thu, Jun 13, 2013 at 2:01 PM, Andre Przywara
wrote:
> For the KVM and XEN hypervisors to be usable, we need to enter the
> kernel in HYP mode. Now that we already are in non-secure state,
> HYP mode switching is within short reach.
>
> While doing the non-secure switch, we have to enab
On Thu, Jun 13, 2013 at 01:01:12PM +0200, Andre Przywara wrote:
> For the KVM and XEN hypervisors to be usable, we need to enter the
> kernel in HYP mode. Now that we already are in non-secure state,
> HYP mode switching is within short reach.
>
> While doing the non-secure switch, we have to enab
For the KVM and XEN hypervisors to be usable, we need to enter the
kernel in HYP mode. Now that we already are in non-secure state,
HYP mode switching is within short reach.
While doing the non-secure switch, we have to enable the HVC
instruction and setup the HYP mode HVBAR (while still secure).
6 matches
Mail list logo