Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964872AbVKGQhF (ORCPT ); Mon, 7 Nov 2005 11:37:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964870AbVKGQhE (ORCPT ); Mon, 7 Nov 2005 11:37:04 -0500 Received: from pollux.ds.pg.gda.pl ([153.19.208.7]:50443 "EHLO pollux.ds.pg.gda.pl") by vger.kernel.org with ESMTP id S964869AbVKGQhD (ORCPT ); Mon, 7 Nov 2005 11:37:03 -0500 Date: Mon, 7 Nov 2005 16:37:09 +0000 (GMT) From: "Maciej W. Rozycki" To: Zachary Amsden Cc: Andi Kleen , linux-kernel@vger.kernel.org Subject: Re: 2.6.14: CR4 not needed to be inspected on the 486 anymore? In-Reply-To: <436F7673.5040309@vmware.com> Message-ID: References: <436A3C10.9050302@vmware.com> <436AA1FD.3010401@vmware.com> <436F7673.5040309@vmware.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: 706 Lines: 16 On Mon, 7 Nov 2005, Zachary Amsden wrote: > While this is at least no worse in the nested fault case than earlier > kernels, I really wish I had one of those weird 486s so I could test the > faulting mechanism. It seems the trap handling code has gotten quite What's so weird about 486s? Besides, for testing it doesn't have to be one -- you will get away with a 386, too. I have neither anymore, but there are people around still using them. 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/