Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752227AbWCQAU5 (ORCPT ); Thu, 16 Mar 2006 19:20:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752451AbWCQAU5 (ORCPT ); Thu, 16 Mar 2006 19:20:57 -0500 Received: from mailout1.vmware.com ([65.113.40.130]:52752 "EHLO mailout1.vmware.com") by vger.kernel.org with ESMTP id S1752227AbWCQAU4 (ORCPT ); Thu, 16 Mar 2006 19:20:56 -0500 Message-ID: <4419DC5D.1020001@vmware.com> Date: Thu, 16 Mar 2006 13:45:01 -0800 From: Zachary Amsden User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Jan Engelhardt Cc: Christoph Hellwig , Linus Torvalds , Linux Kernel Mailing List , Virtualization Mailing List , Xen-devel , Andrew Morton , Dan Hecht , Dan Arai , Anne Holler , Pratap Subrahmanyam , Christopher Li , Joshua LeVasseur , Chris Wright , Rik Van Riel , Jyothy Reddy , Jack Lo , Kip Macy , Jan Beulich , Ky Srinivasan , Wim Coekaerts , Leendert van Doorn Subject: Re: [RFC, PATCH 2/24] i386 Vmi config References: <200603131800.k2DI0RfN005633@zach-dev.vmware.com> <20060314152350.GB16921@infradead.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 16 Jan Engelhardt wrote: > And, the last thing, distributor kernels are often compiled for i586 to > be generic to all users. But some users may actually run them on i686, > and these users would like to have VMI (speculation :-). Which would > include a forceful patch to Kconfig to have the VMI option available > with CONFIG_M586. > We can reenable all these things eventually. We hacked them out to get around some of the awful hacks required for these older machines, (F00F bug protection, broken APICs, etc). - 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/