Date: Thu, 05 Nov 2009 12:52:00 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Kostik Belousov <kostikbel@gmail.com> 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: <86fx8tfau7.fsf@ds4.des.no> In-Reply-To: <20091105112834.GR2331@deviant.kiev.zoral.com.ua> (Kostik Belousov's message of "Thu, 5 Nov 2009 13:28:34 %2B0200") References: <4e6cba830911050302k56bed35aj5ca9fa16379ab325@mail.gmail.com> <20091105112834.GR2331@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fx8tfau7.fsf>