Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753807Ab0DMV67 (ORCPT ); Tue, 13 Apr 2010 17:58:59 -0400 Received: from terminus.zytor.com ([198.137.202.10]:54824 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751662Ab0DMV66 (ORCPT ); Tue, 13 Apr 2010 17:58:58 -0400 Message-ID: <4BC4E8FB.8060802@zytor.com> Date: Tue, 13 Apr 2010 14:58:19 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 MIME-Version: 1.0 To: Yinghai CC: Bjorn Helgaas , Thomas Gleixner , Ingo Molnar , Andy Isaacson , guenter.roeck@ericsson.com, Linus Torvalds , "linux-pci@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Thomas Renninger Subject: Re: [PATCH -v2 1/2] x86: Reserve [0xa0000, 0x100000] in e820 map References: <20100409223532.GC11130@hexapodia.org> <4BBFB1D8.6090802@oracle.com> <20100410000030.GE11130@hexapodia.org> <4BBFD019.9040405@oracle.com> <20100410014308.GG11130@hexapodia.org> <4BBFD8EF.6020108@oracle.com> <20100410015711.GH11130@hexapodia.org> <4BBFE66C.2040603@oracle.com> <20100412185416.GA19959@hexapodia.org> <4BC375D9.4040503@oracle.com> <20100412200224.GO11130@hexapodia.org> <4BC39F67.4090407@oracle.com> <1271192527.6035.44.camel@dc7800.home> <4BC4DD85.5030203@zytor.com> <4BC4DDEA.60202@oracle.com> <4BC4DFAD.9020600@zytor.com> <4BC4E55B.7000103@oracle.com> In-Reply-To: <4BC4E55B.7000103@oracle.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1280 Lines: 33 On 04/13/2010 02:42 PM, Yinghai wrote: > On 04/13/2010 02:18 PM, H. Peter Anvin wrote: >> On 04/13/2010 02:11 PM, Yinghai wrote: >>>> >>>> I guess the real question (which I haven't looked at myself) is if the >>>> E820_RESERVED -> BUSY will cause an explicitly assigned BAR from being >>>> moved. That's bad, not so much for this particular range, but from BARs >>>> which may be assigned by SMM. Hacking that up in a simulator >>>> (Qemu/Bochs) and testing it is probably on the to do list... >>> >>> no, if some device BAR fall in that range, it should still use that range, and will not be relocated. >>> >>> will update the change log. >>> >> >> Good, that's what we want. > > the driver for that device later can not use pci_request_region(). because that region is BUSY already. > That's not good (in general - for devices in this particular range it's not such a big deal, but it is potentially really bad for devices marked reserved for them not to be moved.) We have talked about a need to resolve this before. -hpa -- 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/