Re: [RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

Hi Bandan, On Tue, Jun 6, 2017 at 4:16 PM, Bandan Das wrote: > Jintack Lim writes: > >> From: Christoffer Dall >> >> When running in virtual EL2 we use the shadow EL1 systerm register array >> for the save/restore process,

Re: [RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

Hi Bandan, On Tue, Jun 6, 2017 at 4:16 PM, Bandan Das wrote: > Jintack Lim writes: > >> From: Christoffer Dall >> >> When running in virtual EL2 we use the shadow EL1 systerm register array >> for the save/restore process, so that hardware and especially the memory >> subsystem behaves as code

Re: [RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

Jintack Lim writes: > From: Christoffer Dall > > When running in virtual EL2 we use the shadow EL1 systerm register array > for the save/restore process, so that hardware and especially the memory > subsystem behaves as code written for EL2

Re: [RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

Jintack Lim writes: > From: Christoffer Dall > > When running in virtual EL2 we use the shadow EL1 systerm register array > for the save/restore process, so that hardware and especially the memory > subsystem behaves as code written for EL2 expects while really running > in EL1. > > This works

[RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

From: Christoffer Dall When running in virtual EL2 we use the shadow EL1 systerm register array for the save/restore process, so that hardware and especially the memory subsystem behaves as code written for EL2 expects while really running in EL1. This works great

[RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit

From: Christoffer Dall When running in virtual EL2 we use the shadow EL1 systerm register array for the save/restore process, so that hardware and especially the memory subsystem behaves as code written for EL2 expects while really running in EL1. This works great for EL1 system register