From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422644AbcK3S3b (ORCPT ); Wed, 30 Nov 2016 13:29:31 -0500 Received: from mail-vk0-f50.google.com ([209.85.213.50]:36582 "EHLO mail-vk0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964823AbcK3S3U (ORCPT ); Wed, 30 Nov 2016 13:29:20 -0500 MIME-Version: 1.0 In-Reply-To: <20161130131812.5a99e3ac@lxorguk.ukuu.org.uk> References: <70eac6639f23df8be5fe03fa1984aedd5d40077a.1479598603.git.luto@kernel.org> <20161130131812.5a99e3ac@lxorguk.ukuu.org.uk> From: Andy Lutomirski Date: Wed, 30 Nov 2016 10:28:53 -0800 Message-ID: Subject: Re: [PATCH] x86/boot: Fail the boot if !M486 and CPUID is missing To: One Thousand Gnomes Cc: Andy Lutomirski , X86 ML , Borislav Petkov , "linux-kernel@vger.kernel.org" , Brian Gerst , Matthew Whitehead Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 30, 2016 at 5:18 AM, One Thousand Gnomes wrote: >> Rather than trying to work around these issues, just have the kernel >> fail loudly if it's running on a CPUID-less 486, doesn't have CPUID, >> and doesn't have CONFIG_M486 set. > > NAK > > This still breaks the Geode at the very least and I think the ELAN and > some of the other older socket 7 devices. These have their own config CPU > type (and in some cases *need* it selected) but do not have CPUID. > > Given the cores without CPUID are often post 486 in other respects this > seems a bit odd. In fact I can't help thinking that the problem is that > sync_core tests CONFIG_M486 whereas we should have and test > > HAVE_CPUID > > and set this by processor type (M586/M486/GEODEGX1/GEODE_LX1/Cyrix plus I > think ELAN not having it) > > I'd been wondering why Geode wasn't working on modern kernels, now I > think I know 8) > Ick. Am I understanding correctly that this isn't a regression per se since the affected machines were already broken? If so, let's fix it for real rather than just reverting this patch. --Andy