From owner-cvs-src@FreeBSD.ORG Fri Apr 27 05:26:18 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8211416A404 for ; Fri, 27 Apr 2007 05:26:18 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 4E82E13C45D for ; Fri, 27 Apr 2007 05:26:18 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 47583 invoked from network); 27 Apr 2007 05:26:20 -0000 Received: from ppp-71-139-34-102.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.34.102) by root.org with ESMTPA; 27 Apr 2007 05:26:20 -0000 Message-ID: <46318974.2030804@root.org> Date: Thu, 26 Apr 2007 22:26:12 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.0 (X11/20070424) MIME-Version: 1.0 To: John Baldwin References: <20070425162233.8CCFC16A59E@hub.freebsd.org> <200704251356.35785.jhb@freebsd.org> <462FCEB9.40406@root.org> <200704261148.23501.jhb@freebsd.org> In-Reply-To: <200704261148.23501.jhb@freebsd.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/acpica acpi.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 05:26:18 -0000 John Baldwin wrote: > On Wednesday 25 April 2007 05:57:13 pm Nate Lawson wrote: >> Yes, that should be ok but why not do local first and then push up tree >> if it fails? Semantically, a child of your bus requested the resource >> so most of the time you should be able to handle it. > > Very few resources should really be alloc'd from sysresource though. No PCI > device should be alloc'ing from that for example. It's really only for > special drivers like IPMI (when it's not enumerated as an ACPI device, but > only via SMBIOS tables) where a system resource is reserving it because it is > in use and needs to keep another device (like on PCI where resources aren't > fixed) from using it. Thus, really only a specific allocation of a resource > in sys_resource should ever alloc from that, and all those specific > allocations will fail up in nexus since sys_resource has already claimed > those regions. Ok, I buy that. -- Nate