Gregory Haskins wrote: > Hi Team, > I don't know if anyone here also subscribes to linux-rt-users, but it > seems as though Ingo et. al. rejected my modifications which ran the > smp_call() in a thread (VFCIPI).
It's not surprising. 650 lines including a custom memory allocator is excessive. > So FYI: KVM is still broken on RT and > needs to be addressed. > > In a nutshell, kvm_lock cannot be used as it us today. It either needs > to be a raw_spinlock_t, or the locking needs to be done differently. > The code currently blows up when you shut down a VM running on top of > PREEMPT_RT. Just thought you might want to know. > What about hoisting the lock outside the IPI as I suggested earlier? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
