d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

If new callout scheduled to another CPU and we are using global timer,

Browse Source 
there is high probability that timer is already programmed by some other
CPU. Especially by one that registered this callout, and so active now.
This commit is contained in:
mav 2010-09-21 17:37:28 +00:00
parent 506226a8f9
commit 10e1b075c5
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
sys/kern/kern_clocksource.c
View File

@ -785,14 +785,18 @@ cpu_new_callout(int cpu, int ticks)
}
/*
* If timer is periodic - just update next event time for target CPU.
* If timer is global - there is chance it is already programmed.
*/
if (periodic) {
if (periodic || (timer->et_flags & ET_FLAGS_PERCPU) == 0) {
state->nextevent = state->nexthard;
tmp = hardperiod;
bintime_mul(&tmp, ticks - 1);
bintime_add(&state->nextevent, &tmp);
ET_HW_UNLOCK(state);
return;
if (periodic ||
bintime_cmp(&state->nextevent, &nexttick, >=)) {
ET_HW_UNLOCK(state);
return;
}
}
/*
* Otherwise we have to wake that CPU up, as we can't get present