From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261817AbTILSsM (ORCPT ); Fri, 12 Sep 2003 14:48:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261811AbTILSqw (ORCPT ); Fri, 12 Sep 2003 14:46:52 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:9369 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261807AbTILSpx (ORCPT ); Fri, 12 Sep 2003 14:45:53 -0400 Message-ID: <3F621453.40101@pobox.com> Date: Fri, 12 Sep 2003 14:45:39 -0400 From: Jeff Garzik Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021213 Debian/1.2.1-2.bunk X-Accept-Language: en MIME-Version: 1.0 To: Andi Kleen CC: Adrian Bunk , ebiederm@xmission.com, akpm@osdl.org, richard.brunner@amd.com, linux-kernel@vger.kernel.org, torvalds@osdl.org Subject: Re: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata References: <99F2150714F93F448942F9A9F112634C0638B196@txexmtae.amd.com> <20030911012708.GD3134@wotan.suse.de> <20030910184414.7850be57.akpm@osdl.org> <20030911014716.GG3134@wotan.suse.de> <3F60837D.7000209@pobox.com> <20030911162634.64438c7d.ak@suse.de> <3F6087FC.7090508@pobox.com> <20030912195606.24e73086.ak@suse.de> <3F62098F.9030300@pobox.com> <20030912182216.GK27368@fs.tum.de> <20030912202851.3529e7e7.ak@suse.de> In-Reply-To: <20030912202851.3529e7e7.ak@suse.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andi Kleen wrote: >>config X86_USE_3DNOW >> bool >> depends on MCYRIXIII || MK7 >> default y > > > All 3dnow! code is dynamically patched depending on the CPUID. Note that the people who care most about x86 kernel size, such as people running on brand new 486 and 586 embedded processors (AMD Elan, ...) are precisely the people that don't need the "convenience" of having the feature dynamically patched into the kernel. Removal of CONFIG_SSE2 was wrong for this same reason. 300 bytes here, 300 bytes there, and all this code is adding up quick. We have CONFIG_EMBEDDED to hide such things from your sight, so you don't even have to worry about them... they will always be dynamically patched in your kernels :) Jeff