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

[Xen patchbot -3.0-testing <patchbot-3.0-testing@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID fe8292fecd09225ad78914bd9ec4ac0ee28dcf24
# Parent  809440d54834cd973d95e3033b893ade961d5e07
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>

xen-unstable cset: 0880561d46d19dfd8a5f41efbad40c99b7b5d2c9
committer: Robert Read <robert@xxxxxxxxxxxxx>

diff -r 809440d54834 -r fe8292fecd09 
linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c
--- a/linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c  Thu Dec  8 04:13:06 2005
+++ b/linux-2.6-xen-sparse/arch/xen/i386/kernel/time.c  Sat Dec 10 07: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