Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752536AbbHSGZ0 (ORCPT ); Wed, 19 Aug 2015 02:25:26 -0400 Received: from mail-io0-f180.google.com ([209.85.223.180]:36258 "EHLO mail-io0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751597AbbHSGZY (ORCPT ); Wed, 19 Aug 2015 02:25:24 -0400 MIME-Version: 1.0 In-Reply-To: <20150818040943.GV26431@google.com> References: <1438039809-24957-1-git-send-email-yinghai@kernel.org> <1438039809-24957-26-git-send-email-yinghai@kernel.org> <20150818040943.GV26431@google.com> Date: Tue, 18 Aug 2015 23:25:23 -0700 X-Google-Sender-Auth: dIYeWTOCzmffy0VVayUlRDplZak Message-ID: Subject: Re: [PATCH v3 25/51] PCI: Fix size calculation with old_size on rescan path From: Yinghai Lu To: Bjorn Helgaas Cc: David Miller , Benjamin Herrenschmidt , Wei Yang , TJ , Yijing Wang , Andrew Morton , "linux-pci@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2028 Lines: 41 On Mon, Aug 17, 2015 at 9:09 PM, Bjorn Helgaas wrote: > On Mon, Jul 27, 2015 at 04:29:43PM -0700, Yinghai Lu wrote: >> On booting path, we don't pass realloc at first, and treat all optional just >> as must, in some case we can smaller size/align with optional than must only. >> >> 04:00.0 has four child bridges: 05:01.0, 05:02.0, 05:03.0, 05:04.0 >> pref layout after booting path like followings: >> >> pci 0000:04:00.0: BAR 9: assigned [mem 0x84000000-0x9fffffff 64bit pref] >> pci 0000:05:04.0: BAR 9: assigned [mem 0x88000000-0x9fffffff 64bit pref] >> pci 0000:05:03.0: BAR 9: assigned [mem 0x84000000-0x841fffff 64bit pref] >> pci 0000:07:00.0: BAR 0: assigned [mem 0x81200000-0x8123ffff 64bit] >> pci 0000:05:03.0: PCI bridge to [bus 08-0f] >> pci 0000:05:03.0: bridge window [mem 0x84000000-0x841fffff 64bit pref] >> pci 0000:10:00.0: BAR 0: assigned [mem 0x90000000-0x9fffffff 64bit pref] >> pci 0000:10:00.0: BAR 2: assigned [mem 0x88000000-0x8800ffff 64bit pref] >> pci 0000:05:04.0: PCI bridge to [bus 10] >> pci 0000:05:04.0: bridge window [mem 0x88000000-0x9fffffff 64bit pref] >> pci 0000:04:00.0: PCI bridge to [bus 05-10] >> pci 0000:04:00.0: bridge window [mem 0x84000000-0x9fffffff 64bit pref] > > Unless 07:00.0 and 10:00.0 are relevant, please remove them. ok > >> so the old size in rescan for 04:00.0 would be 0x1c000000, and align is 0x4000000 >> >> during remove and rescan: >> >> pci 0000:05:03.0: bridge window [mem 0x00000000-0xffffffffffffffff 64bit pref] to [bus 08-0f] add_size 200000 add_align 100000 alt_size 0 alt_align 0 must_size 0 must_align 0 > > What is "[mem 0x00000000-0xffffffffffffffff 64bit pref]" telling us? > Surely that's not an actual aperture, is it? required size is 0, the optional only resources. -- 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/