From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f174.google.com ([209.85.220.174]:41534 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754694Ab2E2SRL convert rfc822-to-8bit (ORCPT ); Tue, 29 May 2012 14:17:11 -0400 MIME-Version: 1.0 In-Reply-To: <4FC50E09.4000204@zytor.com> References: <1337754877-19759-1-git-send-email-yinghai@kernel.org> <1337754877-19759-3-git-send-email-yinghai@kernel.org> <20120525043651.GA1391@google.com> <20120525193716.GA8817@google.com> <4FC50E09.4000204@zytor.com> Date: Tue, 29 May 2012 11:17:10 -0700 Message-ID: Subject: Re: [PATCH 02/11] PCI: Try to allocate mem64 above 4G at first From: Yinghai Lu To: "H. Peter Anvin" Cc: Bjorn Helgaas , Linus Torvalds , Steven Newbury , Andrew Morton , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-pci-owner@vger.kernel.org List-ID: On Tue, May 29, 2012 at 10:57 AM, H. Peter Anvin wrote: > On 05/29/2012 10:55 AM, Yinghai Lu wrote: >> >> x86 are using 16bits. >> >> some others use 32 bits. >> #define IO_SPACE_LIMIT 0xffffffff >> >> ia64 and sparc are using 64bits. >> #define IO_SPACE_LIMIT               0xffffffffffffffffUL >> >> but pci only support 16bits and 32bits. >> >> maybe later we can add >> PCI_MAX_RESOURCE_16 >> >> to handle 16bits and 32bit io ports. >> > > Shouldn't this be dealt by root port apertures? > pci bridge could support 16bits and 32bits io port. but we did not record if 32bits is supported. so during allocating, could have allocated above 64k address to non 32bit bridge. but x86 is ok, because ioport.end always set to 0xffff. other arches with IO_SPACE_LIMIT with 0xffffffff or 0xffffffffffffffffUL may have problem. Yinghai