Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754566AbaLIXNw (ORCPT ); Tue, 9 Dec 2014 18:13:52 -0500 Received: from mail-ie0-f177.google.com ([209.85.223.177]:51962 "EHLO mail-ie0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754471AbaLIXNu (ORCPT ); Tue, 9 Dec 2014 18:13:50 -0500 MIME-Version: 1.0 In-Reply-To: References: <1418160871-5605-1-git-send-email-yinghai@kernel.org> Date: Tue, 9 Dec 2014 15:13:49 -0800 X-Google-Sender-Auth: oQl5-n9IT7G053HyEcTsdGhcnZE Message-ID: Subject: Re: [PATCH] PCI: Clear all bridge res MEM_64 if host bridge has non mem64 From: Yinghai Lu To: Bjorn Helgaas Cc: Gavin Shan , Benjamin Herrenschmidt , =?UTF-8?Q?Marek_Kord=C3=ADk?= , Alexey Voronkov , Wei Yang , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 9, 2014 at 1:53 PM, Bjorn Helgaas wrote: > On Tue, Dec 9, 2014 at 2:34 PM, Yinghai Lu wrote: >> + list_for_each_entry(window, &bridge->windows, list) { >> + res = window->res; >> + if (resource_type(res) == IORESOURCE_MEM || >> + res->end > 0xffffffff) { >> + bridge->has_mem64_res = true; > > This is an interesting idea, but I think you're checking CPU addresses > here, and you need to check PCI bus addresses. Looks like those IBM platforms have res > 4g, but pci bus address < 4g. If we check pci bus address, and then we would break those platforms. Yinghai -- 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/