<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/ 1/15 09:16 PM, Alexey Eromenko
wrote:<br>
</div>
<blockquote
cite="mid:CAOJ6w=H04cT_wc+dRy98_4n4o124qDcuFwKPfz_fO+OYviPJAw@mail.gmail.com"
type="cite">
<pre wrap="">Basically VirtualBox is going to implement ABI compatible with Hyper V and
with KVM on the host side.
</pre>
</blockquote>
<br>
Correct. At present, this is providing paravirtualized clock support
and a little bit more like spinlocks for KVM guests.<br>
<br>
With Hyper-V provider, this should also result in relaxing timer
checks within Windows guests, so BSODs like "A clock interrupt was
not received on a secondary processor within the allocated time
interval" would be avoided.<br>
<br>
This also results in slightly less overhead by not having to
intercept any guest RDTSC instructions by the hypervisor once the
guest has started using the paravirtualized clocks. However, these
are difficult to benchmark; you would need very specific workloads
triggering a huge amount of TSC reads on SMP VMs.<br>
<br>
Regards,<br>
Ram.<br>
<br>
<br>
<blockquote
cite="mid:CAOJ6w=H04cT_wc+dRy98_4n4o124qDcuFwKPfz_fO+OYviPJAw@mail.gmail.com"
type="cite">
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a>
<a class="moz-txt-link-freetext" href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>