Date: Wed, 18 Jan 2017 09:00:52 +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: <24593c49-b0d5-8aaf-e11b-bfef4704267e@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
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() ? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24593c49-b0d5-8aaf-e11b-bfef4704267e>