From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751218AbWFUAkp (ORCPT ); Tue, 20 Jun 2006 20:40:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751877AbWFUAkp (ORCPT ); Tue, 20 Jun 2006 20:40:45 -0400 Received: from mailout1.vmware.com ([65.113.40.130]:28619 "EHLO mailout1.vmware.com") by vger.kernel.org with ESMTP id S1751218AbWFUAkp (ORCPT ); Tue, 20 Jun 2006 20:40:45 -0400 Message-ID: <4498958B.504@vmware.com> Date: Tue, 20 Jun 2006 17:40:43 -0700 From: Zachary Amsden User-Agent: Thunderbird 1.5.0.4 (X11/20060516) MIME-Version: 1.0 To: Jeremy Fitzhardinge Cc: Linux Kernel Mailing List , Andrew Morton , Chris Wright , Christian Limpach , jeremy@xensource.com Subject: Re: [PATCH 2.6.17] Clean up and refactor i386 sub-architecture setup References: <44988803.5090305@goop.org> <44988E08.9070000@vmware.com> <449891B9.3060409@goop.org> In-Reply-To: <449891B9.3060409@goop.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jeremy Fitzhardinge wrote: > Zachary Amsden wrote: >> This looks awesome. Are there any plans to get these >> sub-architectures to work with the generic subarch? Seems the next >> logical step would be putting each mach-*/*.o into separated namespaces. > > I haven't looked at that. This patch was intended to be a very simple > uncontroversial rearrangement, in preparation for the Xen subarch, and > to just clean up a corner of the kernel which seems to have gotten a > bit warty. Chris just sent me your patches from March which look like > they cover a lot of the same ground, but I haven't looked at them in > detail yet. This is cleaner than the patches I sent in March, although we want to re-use parts of the mach-default code, not replace it entirely. Hence my interest in the multi-subarch generic kernel. I'd be glad to look into it. Zach