Xen devel - Aug 2010 - [PATCH 04/14] Nested Virtualization: function hooks

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> +int hvm_nestedhvm_vcpu_vmentry(struct vcpu *v)
> +{
> +    if (hvm_funcs.nestedhvm_vcpu_vmentry)
> +        return hvm_funcs.nestedhvm_vcpu_vmentry(v);
> +    return -EOPNOTSUPP;
> +}
I am not sure if we need a generic vmentry here. Will this require us to
pre-read many vendor specific control state (i.e. vmcs & vmcs field) into a
common data structure. From patch 10, it seems yes. Then it may be an
overwhelmed access to VMCS registers.
> +
> +int hvm_nestedhvm_vcpu_vmexit(struct vcpu *v, struct cpu_user_regs
> *regs, +                             uint64_t exitcode)
> +{
> +    if (hvm_funcs.nestedhvm_vcpu_vmexit)
> +        return hvm_funcs.nestedhvm_vcpu_vmexit(v, regs, exitcode);
> +    return -EOPNOTSUPP;
> +}
> +
ditto

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel