Date: Tue, 17 Jan 2017 17:14:31 -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: <98986414.HD1czBRNas@ralph.baldwin.cx> In-Reply-To: <9d0f6789-35cf-7fed-643a-237ddb29f373@selasky.org> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <11f27a15-f9bc-8988-a17e-78aeff1745fb@selasky.org> <9d0f6789-35cf-7fed-643a-237ddb29f373@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98986414.HD1czBRNas>