From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: [PATCH v10 4/7] PCI: add SR-IOV API for Physical Function driver Date: Fri, 06 Mar 2009 13:48:33 -0800 Message-ID: <49B19A31.6070205@xenotime.net> References: <1235112888-9524-1-git-send-email-yu.zhao@intel.com> <1235112888-9524-5-git-send-email-yu.zhao@intel.com> <20090306203717.GG25995@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Yu Zhao , jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Matthew Wilcox Return-path: In-Reply-To: <20090306203717.GG25995@parisc-linux.org> Sender: linux-pci-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Matthew Wilcox wrote: > On Fri, Feb 20, 2009 at 02:54:45PM +0800, Yu Zhao wrote: > >> + if (nres != iov->nres) { >> + dev_err(&dev->dev, "no enough MMIO for SR-IOV\n"); >> + return -ENOMEM; >> + } "not enough MMIO BARs for SR-IOV" or "not enough MMIO resources for SR-IOV" or "too few MMIO BARs for SR-IOV" ? > Randy, can you help us out with better wording here? > >> + dev_err(&dev->dev, "no enough bus range for SR-IOV\n"); > > and here. "SR-IOV: bus number too large" or "SR-IOV: bus number out of range" or "SR-IOV: cannot allocate valid bus number" ? >> + if (iov->link != dev->devfn) { >> + rc = -ENODEV; >> + list_for_each_entry(link, &dev->bus->devices, bus_list) { >> + if (link->sriov && link->devfn == iov->link) >> + rc = sysfs_create_link(&iov->dev.kobj, >> + &link->dev.kobj, "dep_link");