From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f46.google.com ([209.85.213.46]:35542 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755890Ab2E2Xrx convert rfc822-to-8bit (ORCPT ); Tue, 29 May 2012 19:47:53 -0400 Received: by yhmm54 with SMTP id m54so2822752yhm.19 for ; Tue, 29 May 2012 16:47:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: 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> From: Bjorn Helgaas Date: Tue, 29 May 2012 17:47:31 -0600 Message-ID: Subject: Re: [PATCH 02/11] PCI: Try to allocate mem64 above 4G at first To: Yinghai Lu Cc: "H. Peter Anvin" , 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 5:33 PM, Yinghai Lu wrote: > On Tue, May 29, 2012 at 4:27 PM, Bjorn Helgaas wrote: >> I don't understand this one at all.  It looks like you mashed together >> at least two changes: (1) prefer I/O space above 64K if available, and >> (2) mark secondary bus resources with IORESOURCE_IO_32 when the P2P >> bridge I/O window address decode type is PCI_IO_RANGE_TYPE_32 and use >> that to limit allocations. > > let drop the one about IORESOURCE_IO_32. > > that should only fix one reallocation bug in theory out of x86. If there's a bug, we should try to fix it. I just don't understand what the bug *is*.