Re: Strange issue after early AP startup

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