On 01/11/2010 12:13 PM, Jan Kiszka wrote:
BTW, does anybody know how to back-port synchronize_srcu_expedited best? It looked like a simple mapping to synchronize_srcu was not sufficient to achieve the same performance as with the pre-srcu locking (e.g. guest&host stalled during guest's framebuffer setup).
Isn't it sufficient to backport kernel/srcu.c? I thought no sched.c changes were necessary.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
