search for: schedule_lock

...======== STATUS ================== I do the heavy load test of create/destroy. CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of code. It makes error. The reason is that atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock. (spin_lock(&schedule_data[cpu].schedule_lock)) This lock-less "pausecnt" makes vcpu_running state changing during the lock of spin_lock_irq(&schedule_data[cpu].schedule_lock)@__enter_schduler(). The code of cshed_schedule exists within this lock. =================== REPRODUCE THE ERROR =================== This problem occur...

...200 +++ 2009-07-10/xen/common/schedule.c 2009-07-15 10:03:11.000000000 +0200 @@ -918,7 +918,7 @@ void __init scheduler_init(void) open_softirq(SCHEDULE_SOFTIRQ, schedule); - for_each_cpu ( i ) + for_each_possible_cpu ( i ) { spin_lock_init(&per_cpu(schedule_data, i).schedule_lock); init_timer(&per_cpu(schedule_data, i).s_timer, s_timer_fn, NULL, i); --- 2009-07-10.orig/xen/common/timer.c 2009-02-18 17:45:17.000000000 +0100 +++ 2009-07-10/xen/common/timer.c 2009-07-15 10:02:46.000000000 +0200 @@ -529,7 +529,7 @@ void __init timer_init(void) SET_HEAP_SIZE(&a...

I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler

Hi,All We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Two platforms (PAE/32E) test all are based on SMP, It means that we boot up SMP guest OS in VMX. Here is the test summary: New issue (1) ================================================ 1) Fails to restore VMX guests http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=929 Issues List (3):