From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([149.20.54.216]:49549 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbbJVBKt (ORCPT ); Wed, 21 Oct 2015 21:10:49 -0400 Date: Wed, 21 Oct 2015 18:27:14 -0700 (PDT) Message-Id: <20151021.182714.551622926534141857.davem@davemloft.net> To: yinghai@kernel.org Cc: helgaas@kernel.org, bhelgaas@google.com, benh@kernel.crashing.org, weiyang@linux.vnet.ibm.com, linux@iam.tj, wangyijing@huawei.com, khalid.aziz@oracle.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 03/60] sparc/PCI: Unify pci_register_region() From: David Miller In-Reply-To: References: <20151021023522.GJ8224@localhost> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-pci-owner@vger.kernel.org List-ID: From: Yinghai Lu Date: Wed, 21 Oct 2015 11:16:53 -0700 > otherwise we need to compare res with pbm->mem_space or pbm->mem64_space > to get direct parent for request_resource_conflict() calling in > pci_register_legacy_regions(). Right, this is the issue. On sparc64, the cpu physical base address used for accessing 64-bit and non-64-bit memory spaces is different. And that's why the resource values will be different.