[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [XenPPC] NAP state
Just as a sanity check, is the intention is to put the processor in the NAP state when .sleep() is invoked? If so, is the following behavior expected? @@ -395,12 +396,34 @@ static void __init __start_xen(multiboot console_endboot(); + while (1) { + long before, after; + before = mftb(); sleep(); after = mftb(); + printk("hid0 = %lx: slept for %ld timebase ticks (%ld seconds)\n", + mfhid0(), after - before, (after - before) / timebase_freq); + } /* Hide UART from DOM0 if we're using it */ serial_endboot(); (XEN) hid0 = 51010180000000: slept for 1952282840 timebase ticks (9 seconds) (XEN) hid0 = 51010180000000: slept for 52834590 timebase ticks (0 seconds) (XEN) hid0 = 51010180000000: slept for 2078791813 timebase ticks (10 seconds) (XEN) hid0 = 51010180000000: slept for 52797943 timebase ticks (0 seconds) (XEN) hid0 = 51010180000000: slept for 2078719926 timebase ticks (10 seconds) (XEN) hid0 = 51010180000000: slept for 52860659 timebase ticks (0 seconds) (XEN) hid0 = 51010180000000: slept for 2078655488 timebase ticks (10 seconds) (XEN) hid0 = 51010180000000: slept for 52932165 timebase ticks (0 seconds) (XEN) hid0 = 51010180000000: slept for 2078598776 timebase ticks (10 seconds) ... _______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ppc-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |