ia64/xen-unstable
changeset 9084:ede16886f979
[IA64] #if 0'd useless code in timer handled.
Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>
Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>
author | awilliam@xenbuild.aw |
---|---|
date | Mon Mar 06 09:09:18 2006 -0700 (2006-03-06) |
parents | c668c6abb5f0 |
children | c4ac21dc3f16 |
files | xen/arch/ia64/xen/xentime.c |
line diff
1.1 --- a/xen/arch/ia64/xen/xentime.c Mon Mar 06 09:06:55 2006 -0700 1.2 +++ b/xen/arch/ia64/xen/xentime.c Mon Mar 06 09:09:18 2006 -0700 1.3 @@ -116,6 +116,12 @@ xen_timer_interrupt (int irq, void *dev_ 1.4 } 1.5 #endif 1.6 #endif 1.7 + 1.8 +#if 0 1.9 + /* Nobody seems to be able to explain this code. 1.10 + It seems to be accumulated tricks, which are not required anymore. 1.11 + Also I have made many tests, I'd like to get confirmation from 1.12 + other site (TG). */ 1.13 if (current->domain == dom0) { 1.14 // FIXME: there's gotta be a better way of doing this... 1.15 // We have to ensure that domain0 is launched before we 1.16 @@ -130,6 +136,7 @@ xen_timer_interrupt (int irq, void *dev_ 1.17 vcpu_wake(dom0->vcpu[0]); 1.18 } 1.19 } 1.20 +#endif 1.21 if (!is_idle_domain(current->domain)) { 1.22 if (vcpu_timer_expired(current)) { 1.23 vcpu_pend_timer(current);