Attached the diff.
Regards,
Ram.
What got changed in VirtualBox for this test build to work? Could you please
provide a patch in advance of the release of 5.0.2?
Although I did not have a problem with my original tests of kernel 4.2-rcX, this
failure happened to me as soon as commit 2ecd9d29abb1 landed in my source. For
the moment, I can run by reverting that kernel commit. I could push a kernel
patch requesting this reversion, but as that commit seems to help performance
for KVM, that might not be a good idea.
Thanks,
Larry
Index: /trunk/src/VBox/Runtime/r0drv/linux/threadctxhooks-r0drv-linux.c
===================================================================
--- /trunk/src/VBox/Runtime/r0drv/linux/threadctxhooks-r0drv-linux.c (revision 100485)
+++ /trunk/src/VBox/Runtime/r0drv/linux/threadctxhooks-r0drv-linux.c (revision 101665)
@@ -191,4 +191,8 @@
pThis->PreemptOps.sched_in = rtThreadCtxHooksLnxSchedIn;
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 2, 0)
+ preempt_notifier_inc();
+#endif
+
*phCtxHook = pThis;
return VINF_SUCCESS;
@@ -220,4 +224,8 @@
Assert(!pThis->fEnabled); /* paranoia */
}
+
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 2, 0)
+ preempt_notifier_dec();
+#endif
ASMAtomicWriteU32(&pThis->u32Magic, ~RTTHREADCTXHOOKINT_MAGIC);
_______________________________________________
vbox-dev mailing list
[email protected]
https://www.virtualbox.org/mailman/listinfo/vbox-dev
