Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265445AbUAEUHS (ORCPT ); Mon, 5 Jan 2004 15:07:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265493AbUAEUHS (ORCPT ); Mon, 5 Jan 2004 15:07:18 -0500 Received: from bolt.sonic.net ([208.201.242.18]:55262 "EHLO bolt.sonic.net") by vger.kernel.org with ESMTP id S265445AbUAEUHP (ORCPT ); Mon, 5 Jan 2004 15:07:15 -0500 Date: Mon, 5 Jan 2004 12:07:07 -0800 From: David Hinds To: linux-kernel@vger.kernel.org Cc: Amit , Russell King Subject: PCI memory allocation bug with CONFIG_HIGHMEM Message-ID: <20040105120707.A18107@sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 835 Lines: 21 In arch/i386/kernel/setup.c we have: /* Tell the PCI layer not to allocate too close to the RAM area.. */ low_mem_size = ((max_low_pfn << PAGE_SHIFT) + 0xfffff) & ~0xfffff; if (low_mem_size > pci_mem_start) pci_mem_start = low_mem_size; which is meant to round up pci_mem_start to the nearest 1 MB boundary past the top of physical RAM. However this does not consider highmem. Should this just be using max_pfn rather than max_low_pfn? (I have a report of this failing on a laptop with a highmem kernel, causing a PCI memory resource to be allocated on top of a RAM area) -- Dave - 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/