[Xen-bugs] [Bug 766] do_block() can cause the domain to never be scheduled again.

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=766





------- Comment #3 from jimix@xxxxxxxxxxxxxx  2006-09-14 08:58 -------
The patch below (applied to Linux) will allow the issue to be demonstrated on a
UP build and be able to destroy and restart the domain that demonstrates the
problem.

The scenario is that DomU continues until it hits idle/power_save and then
blocks, and yes this is during boot. Without setting the "alarm" this domain
will not get scheduled again until some IO event occurs.  This IO event is
caused by console input to this domain, this should cause it to be scheduled
again but it does not.

Some simple poking by me indicates that the console evtchn seems to be masked,
but it is unclear.

diff -r 4a1f58739bc2 arch/powerpc/platforms/xen/setup.c
--- a/arch/powerpc/platforms/xen/setup.c        Tue Sep 12 15:53:01 2006 -0500
+++ b/arch/powerpc/platforms/xen/setup.c        Thu Sep 14 11:49:47 2006 -0400
@@ -170,9 +170,10 @@ static void xen_power_save(void)
        u64 offset_ns = jiffies_to_ns(1);
        int rc;

-       rc = HYPERVISOR_set_timer_op(now_ns + offset_ns);
-       BUG_ON(rc != 0);
-
+       if (is_dom0) {
+               rc = HYPERVISOR_set_timer_op(now_ns + offset_ns);
+               BUG_ON(rc != 0);
+       }
        HYPERVISOR_sched_op(SCHEDOP_block, NULL);
 }



-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs