Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265632AbUAGUaA (ORCPT ); Wed, 7 Jan 2004 15:30:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266314AbUAGUaA (ORCPT ); Wed, 7 Jan 2004 15:30:00 -0500 Received: from caramon.arm.linux.org.uk ([212.18.232.186]:263 "EHLO caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP id S265632AbUAGU36 (ORCPT ); Wed, 7 Jan 2004 15:29:58 -0500 Date: Wed, 7 Jan 2004 20:29:51 +0000 From: Russell King To: "Eric W. Biederman" Cc: Linus Torvalds , Andi Kleen , Mika Penttil? , Andi Kleen , David Hinds , linux-kernel@vger.kernel.org Subject: Re: PCI memory allocation bug with CONFIG_HIGHMEM Message-ID: <20040107202951.B18708@flint.arm.linux.org.uk> Mail-Followup-To: "Eric W. Biederman" , Linus Torvalds , Andi Kleen , Mika Penttil? , Andi Kleen , David Hinds , linux-kernel@vger.kernel.org References: <20040106081203.GA44540@colin2.muc.de> <3FFA7BB9.1030803@kolumbus.fi> <20040106094442.GB44540@colin2.muc.de> <20040106153706.GA63471@colin2.muc.de> <20040107093143.A29200@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from ebiederm@xmission.com on Wed, Jan 07, 2004 at 08:06:04AM -0700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1527 Lines: 37 On Wed, Jan 07, 2004 at 08:06:04AM -0700, Eric W. Biederman wrote: > Russell King writes: > > > On Tue, Jan 06, 2004 at 09:58:23PM -0700, Eric W. Biederman wrote: > > > ffff0000-ffffffff : reserved > > > > > > That last reserved region is 64K. Which looking at the pci registers > > > is technically correct at the moment. Only 64K happen to be decoded. > > > > We already have this distinction between in use (or busy) resources and > > allocated resources. Surely the BIOS ROM region should be an allocation > > resource not a busy resource, so that the MTD driver can obtain a busy > > resource against it? > > Nope the BIOS region is allocated as BUSY, at least as it comes > out of the E820 map. > > >From arch/i386/kernel/setup.c:legacy_init_iomem_resources > .... > res -> start = e820.map[i].addr; > res -> end = res->start + e820.map[i].size - 1; > res -> flags = IORESOURCE_MEM | IORESOURCE_BUSY; > request_resource(&iomem_resource, res); I was hoping someone was going to take my comments as a suggestion for a possible solution to the problem. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core - 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/