|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] The context switch overhead comparison between vmexit/vmentr
Hi,
If I just considering the pure context switch ovehead, which one has bigger
overhead, using HW vmexit/vmentry to do root and non-root mode switch by
programming VT-x vetor or using SW hypercall to inject interrupt to switch
from ring 1 to ring 0 (or ring 3 to ring 0 for 64bit OS)? Does the switch
between ring1 and ring0 has the same overhead as the switch between ring 3
and ring0?
BTW, both root and non-root mode has four rings, if the ring0 and ring3 in
non-root mode are used for guest os kernel and user applications, which ring
level in root mode will be used when doing vmexit?
Thanks,
Liang
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Xen-devel] Re: NUMA and SMP, (continued)
- Re: [Xen-devel] Re: NUMA and SMP, Ryan Harper
- Re: [Xen-devel] Re: NUMA and SMP, Daniel Stodden
- Re: [Xen-devel] Re: NUMA and SMP, Ryan Harper
- Re: [Xen-devel] Re: NUMA and SMP, Daniel Stodden
- Re: [Xen-devel] Re: NUMA and SMP, Ryan Harper
- Re: [Xen-devel] Re: NUMA and SMP, tgh
- Re: [Xen-devel] Re: NUMA and SMP, Ryan Harper
- RE: [Xen-devel] Re: NUMA and SMP, Petersson, Mats
- Re: [Xen-devel] Re: NUMA and SMP, tgh
- Re: [Xen-devel] Re: NUMA and SMP, Ryan Harper
- [Xen-devel] The context switch overhead comparison between vmexit/vmentry and hypercall.,
Liang Yang <=
|
|
|
|
|