Date: Wed, 18 Jan 2017 08:50:48 -0800 From: John Baldwin <jhb@freebsd.org> To: Hans Petter Selasky <hps@selasky.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: <61871203.aVMyyfjlhL@ralph.baldwin.cx> In-Reply-To: <24593c49-b0d5-8aaf-e11b-bfef4704267e@selasky.org> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <3558195.Ack1AKBXSB@ralph.baldwin.cx> <24593c49-b0d5-8aaf-e11b-bfef4704267e@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, January 18, 2017 09:00:52 AM Hans Petter Selasky wrote: > On 01/18/17 02:18, John Baldwin wrote: > > You might still want to adjust 'nextevent' to schedule the next interrupt > > to be sooner than 'timerperiod' though. You could just set 'nextevent' to > > 'now' in that case instead of 'next'. > > Right, I'll give that a spin. Would have to be "now + 1" instead of > "now", due to check before et_start() ? Ugh, ok. + 1 with sbintime_t is kind of odd which is why I would have liked to avoid it, but it seems it is required. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61871203.aVMyyfjlhL>