Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750987AbVKKSAW (ORCPT ); Fri, 11 Nov 2005 13:00:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750990AbVKKSAV (ORCPT ); Fri, 11 Nov 2005 13:00:21 -0500 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:4612 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S1750987AbVKKSAU (ORCPT ); Fri, 11 Nov 2005 13:00:20 -0500 Date: Fri, 11 Nov 2005 18:00:24 +0000 (GMT) From: "Maciej W. Rozycki" To: "H. Peter Anvin" Cc: Pavel Machek , Zachary Amsden , Andrew Morton , Linus Torvalds , Linux Kernel Mailing List , Zwane Mwaikambo , Pratap Subrahmanyam , Christopher Li , "Eric W. Biederman" , Ingo Molnar Subject: Re: [PATCH 1/10] Cr4 is valid on some 486s In-Reply-To: <4374D99C.1080006@zytor.com> Message-ID: References: <200511100032.jAA0WgUq027712@zach-dev.vmware.com> <20051111103605.GC27805@elf.ucw.cz> <4374D99C.1080006@zytor.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 694 Lines: 16 On Fri, 11 Nov 2005, H. Peter Anvin wrote: > I think the 486's that have CR4 are the same that have CPUID, and thus can be > tested for by the presence of the ID flag. That's correct; for our purposes a 486 that would implement CR4 but not CPUID would not be interesting anyway, as we don't use CR4 elsewhere but for features discovered through CPUID. And I don't think there's ever been an implementation that had CPUID but no CR4. Maciej - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/