From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266049AbUAQPSh (ORCPT ); Sat, 17 Jan 2004 10:18:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266052AbUAQPSh (ORCPT ); Sat, 17 Jan 2004 10:18:37 -0500 Received: from stat1.steeleye.com ([65.114.3.130]:12754 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S266049AbUAQPSc (ORCPT ); Sat, 17 Jan 2004 10:18:32 -0500 Subject: Re: [PATCH] Intel Alder IOAPIC fix From: James Bottomley To: "Eric W. Biederman" Cc: Linus Torvalds , Andrew Morton , Linux Kernel In-Reply-To: References: <1073876117.2549.65.camel@mulgrave> <1073948641.4178.76.camel@mulgrave> <1073954751.4178.98.camel@mulgrave> <1074012755.2173.135.camel@mulgrave> <1074185897.1868.118.camel@mulgrave> <1074196460.1868.250.camel@mulgrave> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 17 Jan 2004 10:18:23 -0500 Message-Id: <1074352704.2015.8.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2004-01-16 at 00:32, Eric W. Biederman wrote: > Yes, this is the extreme case. In normal cases I would just > expect to push to one side and probably shrink it to 0. I guess > I have something against implying a hierarchal relationship that > does not exist. Well, it makes sense to me that the resource would be a child of the reserved area, because the reserved area covers the APICs and this rather annoying PCI device has one of the IO APICs tied to BAR0. In this case, we have a PCI device claiming something we already discovered and made use of long ago in bootup. > Right. To me it looks like separate cases. What I keep envisioning > scanning the PCI devices and then realizing they are behind > a bridge. Before I go to far I guess I should ask. > > The splitting/pushing aside looks especially useful for those > cases where you subdivide the resource again. > > As for the bridge case I think that is something different. The pragmatist in me says we can handle them all as a single case. Simply put, it means insert_resource() says "I know this belongs in the resource tree, just put it in where it should go, please". As long as we make sure we only use it for the exception cases, it should all work fine. All I really want is to get the alter 4 and 8 way boxes working again, I'm happy to go with whatever people decide about resources. What other uses are there for the TENTATIVE regions? James