From owner-freebsd-current@freebsd.org  Wed Jan 18 08:00:09 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A31DCB5E1D
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 18 Jan 2017 08:00:09 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 05BB816D1;
 Wed, 18 Jan 2017 08:00:09 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 0A2D01FE025;
 Wed, 18 Jan 2017 08:59:49 +0100 (CET)
Subject: Re: Strange issue after early AP startup
To: John Baldwin <jhb@freebsd.org>
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>
Cc: Ian Lepore <ian@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 Konstantin Belousov <kib@freebsd.org>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <5a6f8c14-3f9c-e51e-4285-5d4ba7a365b9@selasky.org>
Date: Wed, 18 Jan 2017 08:59:33 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <3558195.Ack1AKBXSB@ralph.baldwin.cx>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2017 08:00:09 -0000

On 01/18/17 02:18, John Baldwin wrote:
> Note that 'nextevent' remains a full 'timerperiod' out (now + timerperiod)
> and so the first clock interrupt is still 'timerperiod' time away and
> any callouts are delayed by that amount of time.  Also, I think you could
> set nextcallopt to 'now' rather than 'now + 1'.

Hi,

Does that mean the following piece of code is missing from getnextevent():

>         /* Handle callout events. */
>         if (event > state->nextcall)
>                 event = state->nextcall;

Like getnextcpuevent() is doing?

--HPS