Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757937AbYHaD74 (ORCPT ); Sat, 30 Aug 2008 23:59:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751162AbYHaD7s (ORCPT ); Sat, 30 Aug 2008 23:59:48 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:57421 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751089AbYHaD7r (ORCPT ); Sat, 30 Aug 2008 23:59:47 -0400 Date: Sat, 30 Aug 2008 20:58:22 -0700 (PDT) From: Linus Torvalds To: Yinghai Lu cc: Ivan Kokshaysky , Jordan Crouse , "Rafael J. Wysocki" , Linux Kernel Mailing List , Jeff Garzik , Tejun Heo , Ingo Molnar , David Witbrodt , Andrew Morton , Kernel Testers Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd In-Reply-To: <86802c440808302053r46256f68mf356797a259ad164@mail.gmail.com> Message-ID: References: <86802c440808301314t525d1b75r9afcc73857cf5c79@mail.gmail.com> <86802c440808301550s627dfcb0h7ff8971c8248703a@mail.gmail.com> <86802c440808301639j137ebef1r1ecadeebd351fc03@mail.gmail.com> <86802c440808301727k3e86c816j323eca0fb5e3f4fc@mail.gmail.com> <86802c440808301750w6655bbek557e6a23b8036654@mail.gmail.com> <86802c440808302053r46256f68mf356797a259ad164@mail.gmail.com> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1198 Lines: 36 On Sat, 30 Aug 2008, Yinghai Lu wrote: > > then > 1. we should not probe them in probe.c > 2. at least we should not try to request_resource for them in > pcibios_resource_survey... > > just pretend that they are not existing. You are missing the fact that we need to know where existing resources are, even if we can't do anything about them! Read my explanation from yesterday about why we need to add the e820 resources to the resource map in the first place. Short recap: - we need to populate the resource map with as much possible information about the system as we can.. - .. because when we assign _dynamic_ resources, we need to make sure that they don't clash with random system resources that we don't really otherwise have a lot of visibility into. So the resource tree is not just about resources we control, it's also about resources that others control(led) and we don't necessarily know a lot about. Linus -- 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/