On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote:
> Jintack Lim <jintack@xxxxxxxxxxxxxxx> writes:
> ...
> > +/**
> > + * kvm_arm_setup_shadow_state -- prepare shadow state based on emulated mode
> > + * @vcpu: The VCPU pointer
> > + */
> > +void kvm_arm_setup_shadow_state(struct kvm_vcpu *vcpu)
> > +{
> > + struct kvm_cpu_context *ctxt = &vcpu->arch.ctxt;
> > +
> > + ctxt->hw_pstate = *vcpu_cpsr(vcpu);
> > + ctxt->hw_sys_regs = ctxt->sys_regs;
> > + ctxt->hw_sp_el1 = ctxt->gp_regs.sp_el1;
> > +}
> > +
> > +/**
> > + * kvm_arm_restore_shadow_state -- write back shadow state from guest
> > + * @vcpu: The VCPU pointer
> > + */
> > +void kvm_arm_restore_shadow_state(struct kvm_vcpu *vcpu)
> > +{
> > + struct kvm_cpu_context *ctxt = &vcpu->arch.ctxt;
> > +
> > + *vcpu_cpsr(vcpu) = ctxt->hw_pstate;
> > + ctxt->gp_regs.sp_el1 = ctxt->hw_sp_el1;
> > +}
> > +
> > +void kvm_arm_init_cpu_context(kvm_cpu_context_t *cpu_ctxt)
> > +{
> > + cpu_ctxt->hw_sys_regs = &cpu_ctxt->sys_regs[0];
> > +}
>
>
> IIUC, the *_shadow_state() functions will set hw_* pointers to
> either point to the "real" state or the shadow state to manage L2 ?
> Maybe, it might make sense to make these function names a little more
> generic since they are not dealing with setting the shadow state
> alone.
>
The notion of 'shadow state' is borrowed from shadow page tables, in
which you always load some 'shadow copy' of the 'real value' into the
hardware, so the shadow state is the one that's used for execution by
the hardware.
The shadow state may be the same as the VCPU's EL1 state, for example,
or it may be a modified version of the VCPU's EL2 state, for example.
If you have better suggestions for naming, we're open to that though.
Thanks,
-Christoffer
