Strange issue after early AP startup
Hans Petter Selasky
hps at selasky.org
Wed Jan 18 07:54:40 UTC 2017
Hi,
On 01/18/17 02:18, John Baldwin wrote:
> Also, I think you could
> set nextcallopt to 'now' rather than 'now + 1'.
There is a check in loadtimer() if next == now, and then the event timer
is not started ??
> } else {
> new = getnextevent();
> eq = (new == *next);
> CTR4(KTR_SPARE2, "load at %d: next %d.%08x eq %d",
> curcpu, (int)(new >> 32), (u_int)(new & 0xffffffff), eq);
> if (!eq) {
> *next = new;
> et_start(timer, new - now, 0);
> }
> }
--HPS
More information about the freebsd-current
mailing list