Date: Thu, 5 Nov 2009 14:00:34 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Dag-Erling Sm??rgrav <des@des.no> Cc: Attilio Rao <attilio@freebsd.org>, Giovanni Trematerra <giovanni.trematerra@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: [PATCH] AMD Opteron Rev. E hack Message-ID: <20091105120034.GS2331@deviant.kiev.zoral.com.ua> In-Reply-To: <86fx8tfau7.fsf@ds4.des.no> References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua> <86fx8tfau7.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--p2u4WfPhYOuYlOsk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 05, 2009 at 12:52:00PM +0100, Dag-Erling Sm??rgrav wrote: > Kostik Belousov <kostikbel@gmail.com> writes: > > I think there is no much sense in printing that hack in unused; > > instead, you should print info when option is enabled and vulnerable > > CPU is detected. >=20 > We should *definitely* print a warninhg when a vulnerable CPU is > detected and the option is *not* enabled. How do you justify not > telling the user that you know the machine will crash as soon as he runs > 'make buildworld' with a high -j value? We do not do this for other cpu bugs workarounds, why this should be different. Besides, there were no confirmed reports of this happening in field (I mean the bug manifestation, not make -j panicing or hanging machine :). --p2u4WfPhYOuYlOsk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEUEARECAAYFAkryvmIACgkQC3+MBN1Mb4hCnwCgy/Qo4SIoQBb2rL6D1Ga+BUHu SAoAl3mN/bYQdjidwDCNYBUKxQpKM9E= =n2li -----END PGP SIGNATURE----- --p2u4WfPhYOuYlOsk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091105120034.GS2331>