Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1554567pxf; Fri, 19 Mar 2021 09:38:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwhrnNAVaoHb7GRNLiSqsLIaDzxPwiKkgpE0L2fC4JHxFD5HaoGqBvESkgRKN8AbYg5hgd6 X-Received: by 2002:a17:906:3952:: with SMTP id g18mr5406084eje.104.1616171884213; Fri, 19 Mar 2021 09:38:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616171884; cv=none; d=google.com; s=arc-20160816; b=zL2cqhQ1kSOu/26cYmeYw+RsaOSIJAn71SdoRBgsKNy4mntwKZUj4FvNAfTud7gIx4 MWZtuTHIAXMmL4BTzjsR2rI4DsuHzcJREEOOHde5e1cBoM/+kDuCtsYVM4dLRGz7e0Lb 8Nfyr7rbKab0Hva8Jjm9IyAf7fl6YU9TG50YzbtMDTF0vX7XVPHlTYBzCxglb627Tc6m MiJ9vK0Ruwq/0LTmwnErVw+T75oSB/XOP8u53FzmmQsdfQHaT0c5Luuh2S70th7jh26U b5eM4xn9frwAffR74ka20YVHmeMo4GBeOjZjIpzuL0DVVkfhtQNEfQ5ukw8dfajHFBL8 guBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=VhJdVDXQx8K4GQtrraP0Fapp49CNExxyxi17Q3XMLqs=; b=TLaNxJa4tkh3uG+IsiG5OOW83poQ7yUYyGPs7XeH0jMuRtetbI1dNtUSCT4HQkbrlu MhffQmdoCG/N6xkD5zV/jjxGWx0nukDXz82MANJnZKkg76/0IZM8xkzkP3apcvAHfeWY TiksVKVQa7j2htXCnN17VurTvWt8eqp4dMGkpZ9DEfZIn7YhjYLSkgF3QCDWe8IrK9Cq JWvEPEjxOCbhnq1urgmXwXa60ZrlyhPvQci9Jbs5CIqWKFbwSp2YjbAQjuSqTmYpPaGk bt6CAITMUUVXsPQ+gslcljG6Y3c9jqogNNJsENepqLIPF0pn5siQuOHhVnt5hmRiDX2x Kq2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o21si4538796ejc.724.2021.03.19.09.37.40; Fri, 19 Mar 2021 09:38:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230176AbhCSQfR (ORCPT + 99 others); Fri, 19 Mar 2021 12:35:17 -0400 Received: from verein.lst.de ([213.95.11.211]:46929 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230177AbhCSQey (ORCPT ); Fri, 19 Mar 2021 12:34:54 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 3ED7B68C65; Fri, 19 Mar 2021 17:34:50 +0100 (CET) Date: Fri, 19 Mar 2021 17:34:49 +0100 From: Christoph Hellwig To: Jason Gunthorpe Cc: Christoph Hellwig , Alex Williamson , Max Gurtovoy , Alexey Kardashevskiy , cohuck@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, liranl@nvidia.com, oren@nvidia.com, tzahio@nvidia.com, leonro@nvidia.com, yarong@nvidia.com, aviadye@nvidia.com, shahafs@nvidia.com, artemp@nvidia.com, kwankhede@nvidia.com, ACurrid@nvidia.com, cjia@nvidia.com, yishaih@nvidia.com, mjrosato@linux.ibm.com Subject: Re: [PATCH 8/9] vfio/pci: export nvlink2 support into vendor vfio_pci drivers Message-ID: <20210319163449.GA19186@lst.de> References: <20210309083357.65467-1-mgurtovoy@nvidia.com> <20210309083357.65467-9-mgurtovoy@nvidia.com> <19e73e58-c7a9-03ce-65a7-50f37d52ca15@ozlabs.ru> <8941cf42-0c40-776e-6c02-9227146d3d66@nvidia.com> <20210319092341.14bb179a@omen.home.shazbot.org> <20210319161722.GY2356281@nvidia.com> <20210319162033.GA18218@lst.de> <20210319162848.GZ2356281@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210319162848.GZ2356281@nvidia.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 19, 2021 at 01:28:48PM -0300, Jason Gunthorpe wrote: > The wrinkle I don't yet have an easy answer to is how to load vfio_pci > as a universal "default" within the driver core lazy bind scheme and > still have working module autoloading... I'm hoping to get some > research into this.. Should we even load it by default? One answer would be that the sysfs file to switch to vfio mode goes into the core PCI layer, and that core PCI code would contain a hack^H^H^H^Hhook to first load and bind vfio_pci for that device.