Date: Thu, 25 Jan 2018 17:21:34 -0500 From: Ian FREISLICH <ian.freislich@capeaugusta.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: current <current@freebsd.org> Subject: Re: Insta-reset-bootloop with r328166 and vm.pmap.pcid_enabled=1 Message-ID: <f64e380b-344b-c02f-004a-2c67525134b1@capeaugusta.com> In-Reply-To: <20180125221312.GU55707@kib.kiev.ua> References: <9e533d36-f2ee-58fc-d629-eed7d70645b4@capeaugusta.com> <20180125221312.GU55707@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/25/18 17:13, Konstantin Belousov wrote: > On Thu, Jan 25, 2018 at 04:58:04PM -0500, Ian FREISLICH wrote: >> Hi >> >> I cannot for the life of me recall why I had vm.pmap.pcid_enabled=3D1 se= t >> in loader.conf, but I did.=9A Most likely very historical reasons. >> >> r328166 and later reset without dropping into the debugger during boot, >> no panic message. > Yes, this is how it is currently behaves. > PCID can be used to optimize PTI, see https://reviews.freebsd.org/D13985. > It is used for very differrent algorithm when PTI=3D1, comparing with PTI= =3D0. Maybe there should be an "interlock" on these knobs, although judging from the number of reports I'm the only that shot my foot. Ian --=20 Ian Freislich --=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f64e380b-344b-c02f-004a-2c67525134b1>