| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH 04/14] Nested Virtualization: function hooks
|
To: |
"Dong, Eddie" <eddie.dong@xxxxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx> |
|
Subject: |
RE: [Xen-devel] [PATCH 04/14] Nested Virtualization: function hooks |
|
From: |
"Dong, Eddie" <eddie.dong@xxxxxxxxx> |
|
Date: |
Wed, 18 Aug 2010 16:36:51 +0800 |
|
Accept-language: |
en-US |
|
Acceptlanguage: |
en-US |
|
Cc: |
Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx> |
|
Delivery-date: |
Wed, 18 Aug 2010 01:43:03 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
Thread-index: |
Acs+r2Fi6EYY4EwFRcGHVf4c1zRvUQAAG7nQ |
|
Thread-topic: |
[Xen-devel] [PATCH 04/14] Nested Virtualization: function hooks |
> +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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home