Date: Tue, 17 Jan 2017 22:35:06 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Ian Lepore <ian@freebsd.org>, John Baldwin <jhb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: Strange issue after early AP startup Message-ID: <9d0f6789-35cf-7fed-643a-237ddb29f373@selasky.org> In-Reply-To: <11f27a15-f9bc-8988-a17e-78aeff1745fb@selasky.org> References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org> <2215603.KuBd8pM5Pm@ralph.baldwin.cx> <3cbe6454-82cc-0592-4ee6-3c1552b19f9a@selasky.org> <4212167.Wq8tLU1ohU@ralph.baldwin.cx> <1484682389.86335.166.camel@freebsd.org> <11f27a15-f9bc-8988-a17e-78aeff1745fb@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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()? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9d0f6789-35cf-7fed-643a-237ddb29f373>