35 messages in com.xensource.lists.xen-devel[Xen-devel] The context switch overhe...
FromSent OnAttachments
David Pilger14 Jan 2007 03:55 
Ryan Harper14 Jan 2007 11:00 
Anthony Liguori15 Jan 2007 09:21 
Petersson, Mats16 Jan 2007 02:47 
Emmanuel Ackaouy16 Jan 2007 05:55 
Petersson, Mats16 Jan 2007 06:18 
ron minnich16 Jan 2007 06:50 
Emmanuel Ackaouy16 Jan 2007 08:13 
Petersson, Mats16 Jan 2007 08:30 
tgh20 Mar 2007 06:09 
Petersson, Mats20 Mar 2007 06:19 
tgh20 Mar 2007 06:49 
Daniel Stodden20 Mar 2007 06:51 
Petersson, Mats20 Mar 2007 08:50 
Ryan Harper20 Mar 2007 09:45 
Petersson, Mats20 Mar 2007 09:47 
tgh20 Mar 2007 18:08 
Daniel Stodden20 Mar 2007 19:44 
tgh21 Mar 2007 18:15 
Daniel Stodden22 Mar 2007 03:42 
tgh22 Mar 2007 05:13 
Daniel Stodden22 Mar 2007 05:28 
Ryan Harper22 Mar 2007 06:02 
Daniel Stodden22 Mar 2007 07:55 
Ryan Harper22 Mar 2007 08:11 
Daniel Stodden22 Mar 2007 08:38 
Ryan Harper22 Mar 2007 09:01 
Daniel Stodden22 Mar 2007 09:21 
Ryan Harper22 Mar 2007 10:02 
tgh22 Mar 2007 22:47 
Ryan Harper23 Mar 2007 07:42 
Petersson, Mats23 Mar 2007 07:48 
tgh27 Mar 2007 18:49 
Ryan Harper27 Mar 2007 19:00 
Liang Yang28 Mar 2007 14:24 
Subject:[Xen-devel] The context switch overhead comparison between vmexit/vmentry and hypercall.
From:Liang Yang (mult@hotmail.com)
Date:03/28/2007 02:24:53 PM
List:com.xensource.lists.xen-devel

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