From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMCMK-0003G4-76 for qemu-devel@nongnu.org; Mon, 03 Aug 2015 05:48:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMCMF-000120-Df for qemu-devel@nongnu.org; Mon, 03 Aug 2015 05:48:40 -0400 Received: from mail-vk0-f53.google.com ([209.85.213.53]:33310) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMCMF-00011t-9Z for qemu-devel@nongnu.org; Mon, 03 Aug 2015 05:48:35 -0400 Received: by vkgc186 with SMTP id c186so40673482vkg.0 for ; Mon, 03 Aug 2015 02:48:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <00be01d0cdc3$bb2e87d0$318b9770$@samsung.com> References: <015a01d0c85c$b52b61d0$1f822570$@samsung.com> <20150727152658.3f3740f7@nial.brq.redhat.com> <00da01d0c9dc$b39503e0$1abf0ba0$@samsung.com> <00f401d0c9e3$517efba0$f47cf2e0$@samsung.com> <015b01d0c9f0$0981cd20$1c856760$@samsung.com> <00b601d0cdba$808e3980$81aaac80$@samsung.com> <00be01d0cdc3$bb2e87d0$318b9770$@samsung.com> From: Peter Maydell Date: Mon, 3 Aug 2015 10:48:15 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH v3] hw/arm/virt: Add high MMIO PCI region List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Fedin Cc: QEMU Developers , Igor Mammedov , Paolo Bonzini , Alexander Graf , "Michael S. Tsirkin" On 3 August 2015 at 09:09, Pavel Fedin wrote: > Hi! > >> What I thought you meant was that a non-LPAE kernel didn't >> work at all if we told it about the high-MMIO window (which >> would mean we'd need to *not* put that in the dtb if we >> wanted to avoid breaking non-LPAE guests that didn't care >> about the other window.) > > Current generic PCI driver is not so smart. It simply tries to map all resources using devm_request_resource() in a loop. If a single call fails, the driver thinks that it cannot work and fails. It does not try to ignore inaccessible regions. Then this is a kernel bug and the kernel should be fixed. >> > The behavior which i explained above causes boot problems if our >> > configuration assumes that we boot off emulated PCI device. Because >> > PCI controller becomes unusable. >> >> ...which is what you're saying here. >> >> Which is it? > > I don't understand this last question... I was confused about whether what happened was (a) the high region is just ignored (b) the presence of the high region in the device tree blob causes things which previously worked to stop working It sounds like the answer is (b). > In order to keep this guest working, we need a possibility to > disable the new MMIO region in qemu. At least to omit it from the > device tree. Yes, this is the workaround, which it sounds like we need. thanks -- PMM