From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755164Ab2E2TDl (ORCPT ); Tue, 29 May 2012 15:03:41 -0400 Received: from terminus.zytor.com ([198.137.202.10]:55908 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751380Ab2E2TDk (ORCPT ); Tue, 29 May 2012 15:03:40 -0400 Message-ID: <4FC51D79.6010804@zytor.com> Date: Tue, 29 May 2012 12:03:21 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Yinghai Lu CC: Bjorn Helgaas , Linus Torvalds , Steven Newbury , Andrew Morton , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 02/11] PCI: Try to allocate mem64 above 4G at first 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> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/29/2012 11:17 AM, Yinghai Lu wrote: > > pci bridge could support 16bits and 32bits io port. > but we did not record if 32bits is supported. > Okay, so this is the actual problem, no? > 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. The latter is nonsense, the PCI-side address space is only 32 bits wide. -hpa