From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 28 Jan 2003 02:23:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 28 Jan 2003 02:23:16 -0500 Received: from holomorphy.com ([66.224.33.161]:34984 "EHLO holomorphy") by vger.kernel.org with ESMTP id ; Tue, 28 Jan 2003 02:23:15 -0500 Date: Mon, 27 Jan 2003 23:31:17 -0800 From: William Lee Irwin III To: "Eric W. Biederman" Cc: Dave Hansen , linux-kernel@vger.kernel.org, "Martin J. Bligh" Subject: Re: kexec reboot code buffer Message-ID: <20030128073117.GJ780@holomorphy.com> Mail-Followup-To: William Lee Irwin III , "Eric W. Biederman" , Dave Hansen , linux-kernel@vger.kernel.org, "Martin J. Bligh" References: <3E31AC58.2020802@us.ibm.com> <3E35AAE4.10204@us.ibm.com> <20030128071826.GI780@holomorphy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Organization: The Domain of Holomorphy Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org William Lee Irwin III writes: >> Seriously, just plop down the fresh zone type and all will be well. >> It's really incredibly easy. On Tue, Jan 28, 2003 at 12:28:04AM -0700, Eric W. Biederman wrote: > I will certainly take a look, tracing through that code can get a little > hairy. It can really be approached much more cavalierly than that. The only extant example aside from the original ZONE_DMA32 implementation I've seen is Simon Winwood's MPSS patch, which needed something on the order of 10 lines of code for a fresh zone type (for one arch). And most of the bulk of the ZONE_DMA32 implementation was stringing up the block layer to utilize it, not inserting the new zone type itself. -- wli