On Fri, Sep 14, 2012 at 5:21 PM, Pablo Sanchez <[email protected]> wrote:
> Usually applications don't spend too much time in kernel space so most
> of the time is spent in user space.

Yes but I thought that virtualization was a special case where the
vbox kernel module did most of the cpu virtualization and tricks
(calling amd-v etc, setting registers etc... although I guess that
with amd-v most of the work is offloaded to the hardware rather than
being a tight loop like in software cpu emulation -bochs, QEmu etc-).

Perhaps someone from the VB team can comment? how is the Virtualbox
software layer? is there a nice diagram somewhere?

FC

------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:  
mailto:[email protected]?subject=unsubscribe

Reply via email to