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=-6.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 00264C433E6 for ; Fri, 12 Mar 2021 18:35:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B7AFD64F70 for ; Fri, 12 Mar 2021 18:35:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233635AbhCLSfC (ORCPT ); Fri, 12 Mar 2021 13:35:02 -0500 Received: from mail.kernel.org ([198.145.29.99]:43566 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233756AbhCLSei (ORCPT ); Fri, 12 Mar 2021 13:34:38 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 76CF364F5B; Fri, 12 Mar 2021 18:34:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615574078; bh=eBRGUpzOaiG5s/KUQiDidE3SFCB985o0uUgGmkVc+7Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jUXTQMMT4xJUisClB8arBD8gM7tXact5Bf9ae/m0vxPmf25EdtjZc/lchUomrMr4L /48tlBwvJ76SwgO5bNIWJxvvTrcoCjBVwWnPqIU0xMmvPuixxy6oDWVKY69c6fzeyW 8sYRPwS1GxbSJH6A+huhqLafajZtRNA4QcGjtsJHeSIcOGmMW8ozZRx4u2Ecxr0AYj Y8hLJmGUYwXz4NI1aKezPsd+rvIQ4XAr5NhaBooytorb/exulIyrlQYwgEA6RpawNj SF90jzZhNBz8183tpzY905dSdLOkNxL/r42lYlCTNLazc2fkBIMmEn4bktu/+AQJvC 11sHQomgrHM0A== Date: Fri, 12 Mar 2021 20:34:33 +0200 From: Leon Romanovsky To: Jason Gunthorpe Cc: Alexander Duyck , Bjorn Helgaas , Bjorn Helgaas , Saeed Mahameed , Jakub Kicinski , linux-pci , linux-rdma@vger.kernel.org, Netdev , Don Dutile , Alex Williamson , "David S . Miller" , Greg Kroah-Hartman Subject: Re: [PATCH mlx5-next v7 0/4] Dynamically assign MSI-X vectors count Message-ID: References: <20210311181729.GA2148230@bjorn-Precision-5520> <20210311201929.GN2356281@nvidia.com> <20210311232059.GR2356281@nvidia.com> <20210312170319.GG2356281@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210312170319.GG2356281@nvidia.com> Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Fri, Mar 12, 2021 at 01:03:19PM -0400, Jason Gunthorpe wrote: > On Fri, Mar 12, 2021 at 08:59:38AM -0800, Alexander Duyck wrote: > > > Lastly by splitting out the onlining step you can avoid potentially > > releasing a broken VF to be reserved if there is some sort of > > unrecoverable error between steps 2 and 3. > > If the PF FW gets in a state that it can't respond to a trivial > command like this then *every* VF is broken. It not a useful scenario > to focus on. Right, many VF initial configurations are done through PF. It MUST work. Thanks > > Jason