On Tue, 19 Feb 2019 13:43:49 +0100
Christoffer Dall wrote:
> On Mon, Feb 18, 2019 at 03:10:49PM +, André Przywara wrote:
> > On Thu, 24 Jan 2019 15:00:30 +0100
> > Christoffer Dall wrote:
> >
> > Hi,
> >
> > > VHE systems don't have to emulate the physical timer, we can simply
> > > assi
On Tue, Feb 19, 2019 at 11:39:50AM +, Alexandru Elisei wrote:
>
> On 1/24/19 2:00 PM, Christoffer Dall wrote:
> > VHE systems don't have to emulate the physical timer, we can simply
> > assigne the EL1 physical timer directly to the VM as the host always
> > uses the EL2 timers.
> >
> > In ord
On Mon, Feb 18, 2019 at 03:10:49PM +, André Przywara wrote:
> On Thu, 24 Jan 2019 15:00:30 +0100
> Christoffer Dall wrote:
>
> Hi,
>
> > VHE systems don't have to emulate the physical timer, we can simply
> > assigne the EL1 physical timer directly to the VM as the host always
> > uses the E
On 1/24/19 2:00 PM, Christoffer Dall wrote:
> VHE systems don't have to emulate the physical timer, we can simply
> assigne the EL1 physical timer directly to the VM as the host always
> uses the EL2 timers.
>
> In order to minimize the amount of cruft, AArch32 gets definitions for
> the physical
On Thu, 24 Jan 2019 15:00:30 +0100
Christoffer Dall wrote:
Hi,
> VHE systems don't have to emulate the physical timer, we can simply
> assigne the EL1 physical timer directly to the VM as the host always
> uses the EL2 timers.
>
> In order to minimize the amount of cruft, AArch32 gets definitio
VHE systems don't have to emulate the physical timer, we can simply
assigne the EL1 physical timer directly to the VM as the host always
uses the EL2 timers.
In order to minimize the amount of cruft, AArch32 gets definitions for
the physical timer too, but is should be generally unused on this
arc
