Strange issue after early AP startup

John Baldwin jhb at freebsd.org
Wed Jan 18 01:20:56 UTC 2017


On Tuesday, January 17, 2017 10:35:06 PM Hans Petter Selasky wrote:
> On 01/17/17 22:28, Hans Petter Selasky wrote:
> > +                       state->nextcall = SBT_MAX;
> > +                       state->nextcallopt = now + 1;
> 
> BTW: What locks are protecting the update of these fields? Can they be 
> written simultaneously by configtimer() and cpu_new_callout()?

Both functions do ET_HW_LOCK() of DPCPU_PTR(timerstate).

-- 
John Baldwin


More information about the freebsd-current mailing list