[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-changelog] Initilaise new cpu's processed-time value from cpu0's



# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 0880561d46d19dfd8a5f41efbad40c99b7b5d2c9
# Parent  fc8d01a6dcacb0429e332dbf8f826d6aae5a420d
Initilaise new cpu's processed-time value from cpu0's 
timestamp. The new cpu's timestamp is not initialised yet,
so should not be used.

Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

diff -r fc8d01a6dcac -r 0880561d46d1 
linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c
--- a/linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c  Sat Dec 10 15:07:03 2005
+++ b/linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c  Sat Dec 10 15:21:43 2005
@@ -872,8 +872,9 @@
 
        do {
                seq = read_seqbegin(&xtime_lock);
+               /* Use cpu0 timestamp: cpu's shadow is not initialised yet. */
                per_cpu(processed_system_time, cpu) = 
-                       per_cpu(shadow_time, cpu).system_timestamp;
+                       per_cpu(shadow_time, 0).system_timestamp;
        } while (read_seqretry(&xtime_lock, seq));
 
        sprintf(timer_name[cpu], "timer%d", cpu);

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.