Date: Wed, 18 Jan 2017 08:54:04 +0100 From: Hans Petter Selasky <hps@selasky.org> To: John Baldwin <jhb@freebsd.org> Cc: Ian Lepore <ian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: Strange issue after early AP startup Message-ID: <dc54eba5-cf88-dfc8-318d-bfc06c750fb4@selasky.org> In-Reply-To: <3558195.Ack1AKBXSB@ralph.baldwin.cx> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <1484682389.86335.166.camel@freebsd.org> <11f27a15-f9bc-8988-a17e-78aeff1745fb@selasky.org> <3558195.Ack1AKBXSB@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dc54eba5-cf88-dfc8-318d-bfc06c750fb4>