From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (bilbo.ozlabs.org [103.22.144.67]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3yWlyt3RsSzDr5J for ; Wed, 8 Nov 2017 10:30:14 +1100 (AEDT) In-Reply-To: <20170927065231.20382-1-aik@ozlabs.ru> To: Alexey Kardashevskiy , linuxppc-dev@lists.ozlabs.org From: Michael Ellerman Cc: Alexey Kardashevskiy , linux-pci@vger.kernel.org, Gavin Shan , kvm-ppc@vger.kernel.org, Yongji Xie , Paul Mackerras , Bjorn Helgaas , David Gibson Subject: Re: [kernel, v2] powerpc/powernv: Reserve a hole which appears after enabling IOV Message-Id: <3yWlys6rlfz9s7C@ozlabs.org> Date: Wed, 8 Nov 2017 10:30:13 +1100 (AEDT) List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2017-09-27 at 06:52:31 UTC, Alexey Kardashevskiy wrote: > In order to make generic IOV code work, the physical function IOV BAR > should start from offset of the first VF. Since M64 segments share > PE number space across PHB, and some PEs may be in use at the time > when IOV is enabled, the existing code shifts the IOV BAR to the index > of the first PE/VF. This creates a hole in IOMEM space which can be > potentially taken by some other device. > > This reserves a temporary hole on a parent and releases it when IOV is > disabled; the temporary resources are stored in pci_dn to avoid > kmalloc/free. > > Cc: linux-pci@vger.kernel.org > Cc: Benjamin Herrenschmidt > Cc: Bjorn Helgaas > Signed-off-by: Alexey Kardashevskiy > Acked-by: Bjorn Helgaas Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/d6f934fd48803d9e58040e2cbab2fe cheers