Date: Tue, 17 Jan 2017 18:37:27 +0100 From: Hans Petter Selasky <hps@selasky.org> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: Strange issue after early AP startup Message-ID: <b4c47ee8-a545-b1b7-b25c-73d9fd9e9a12@selasky.org> In-Reply-To: <2215603.KuBd8pM5Pm@ralph.baldwin.cx> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <3466870.vFI8cjabAc@ralph.baldwin.cx> <264c5dd8-d82d-3326-7de5-96b0bb96ac01@selasky.org> <2215603.KuBd8pM5Pm@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/17/17 16:50, John Baldwin wrote: > (One odd thing is that even in your case the first call to handleevents(), > the 'now => state->nextcallout' check in handleevents() should be true > which resets both nextcall and nextcallopt and invokes callout_process().) Hi, I suspect the cpu_new_callout() function is changing this condition after a callout_reset() call, before handleevents() gets a chance to run. I'll give your patch a spin right away and let you know how it goes. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b4c47ee8-a545-b1b7-b25c-73d9fd9e9a12>