From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD560C0650E for ; Wed, 3 Jul 2019 13:59:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A5ACD218A3 for ; Wed, 3 Jul 2019 13:59:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562162385; bh=9jZQ+xkADDFcvlMkther+QWiQF9N7WPn19dHdCUcdJQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=wGmTYod9skwIAWVu7YjOrTSoj6/4wOej+ApIGnHWXl+T/AgqfAN7byNFhgg28MieE 5+FCb7ZTeb5XG5xPVDfHMlgKTOnfh6r5UAo5AzM0aQGMLgHHHvFLiPWFctVGQguees u4aOMSovK6tabzap+xDGH9rDerjvg87oDZT2FucY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726430AbfGCN7p (ORCPT ); Wed, 3 Jul 2019 09:59:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:41538 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725830AbfGCN7o (ORCPT ); Wed, 3 Jul 2019 09:59:44 -0400 Received: from localhost (84.sub-174-234-39.myvzw.com [174.234.39.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6F41E218A4; Wed, 3 Jul 2019 13:59:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562162383; bh=9jZQ+xkADDFcvlMkther+QWiQF9N7WPn19dHdCUcdJQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vrOSy5n7+9jskmOih+YCm2qC0fiZpZUcrmgqI0SUk1XzVg5r8xd9SZ7WGFWNP8jk0 lTtiqUFV35QEFa+QYJ9vOJf3jUQrXQSDj8Xb+Yn2RODFehXFcct8+Yy0LdhyIzpKH2 19gu9RidHEYafUdvqQaslt+8Az+TYsWmWf5IQ8Sg= Date: Wed, 3 Jul 2019 08:59:41 -0500 From: Bjorn Helgaas To: Alex Williamson Cc: linux-pci@vger.kernel.org, Kuppuswamy Sathyanarayanan , KarimAllah Ahmed , Hao Zheng , linux-kernel@vger.kernel.org, nanhai.zou@linux.alibaba.com, quan.xu0@linux.alibaba.com, ashok.raj@intel.com, keith.busch@intel.com, mike.campin@intel.com Subject: Re: [PATCH 0/2] PCI/IOV: Resolve regression in SR-IOV VF cfg_size Message-ID: <20190703135941.GL128603@google.com> References: <156046609596.29869.5839964168034189416.stgit@gimli.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <156046609596.29869.5839964168034189416.stgit@gimli.home> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Thu, Jun 13, 2019 at 04:56:57PM -0600, Alex Williamson wrote: > The commit reverted in the first patch introduced a regression where > only the first VF reports the correct config space size, subsequent VFs > report 256 bytes of config space. Replace this in the second patch > with an assumption that all VFs support extended config space by virtue > of the SR-IOV spec requiring a PCIe capability and reachability of the > PF extended config space already being proven by the existence of the > VF. Thanks, > > Alex > > --- > > Alex Williamson (2): > Revert: PCI/IOV: Use VF0 cached config space size for other VFs > PCI/IOV: Assume SR-IOV VFs support extended config space. Applied to pci/virtualization for v5.3 with Kuppuswamy's reviewed-by on 2/2, thanks! > drivers/pci/iov.c | 2 -- > drivers/pci/pci.h | 1 - > drivers/pci/probe.c | 26 ++++++++++++-------------- > 3 files changed, 12 insertions(+), 17 deletions(-)