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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DC92AC352A1 for ; Wed, 7 Dec 2022 16:35:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229623AbiLGQfR (ORCPT ); Wed, 7 Dec 2022 11:35:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57992 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229684AbiLGQfP (ORCPT ); Wed, 7 Dec 2022 11:35:15 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C0EA356560; Wed, 7 Dec 2022 08:35:13 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id DC7F367373; Wed, 7 Dec 2022 17:35:06 +0100 (CET) Date: Wed, 7 Dec 2022 17:35:06 +0100 From: Christoph Hellwig To: Max Gurtovoy Cc: Christoph Hellwig , Jason Gunthorpe , Lei Rao , kbusch@kernel.org, axboe@fb.com, kch@nvidia.com, sagi@grimberg.me, alex.williamson@redhat.com, cohuck@redhat.com, yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com, mjrosato@linux.ibm.com, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, kvm@vger.kernel.org, eddie.dong@intel.com, yadong.li@intel.com, yi.l.liu@intel.com, Konrad.wilk@oracle.com, stephen@eideticom.com, hang.yuan@intel.com Subject: Re: [RFC PATCH 1/5] nvme-pci: add function nvme_submit_vf_cmd to issue admin commands for VF driver. Message-ID: <20221207163506.GA2010@lst.de> References: <20221206135810.GA27689@lst.de> <20221206153811.GB2266@lst.de> <20221206165503.GA8677@lst.de> <20221207075415.GB2283@lst.de> <4f11e0bb-e090-bf9b-4f98-578273865200@nvidia.com> <20221207134644.GB21691@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 07, 2022 at 04:50:00PM +0200, Max Gurtovoy wrote: > When we perform step #3 we are narrowing it's scope and maybe some caps > that you're concerned of. After this setting, the controlled function is in > LM mode (we should define what does that mean in order to be able to > migrate it correctly) and the controlling function is the migration master > of it. Both can be aware of that. The only one that can master the > controlled function is the controlling function in LM mode. Thus, it will > be easy to keep that handle inside the kernel for VFs and for MDEVs as > well. Maybe. So you'd introduce a kernel linkage that both side would have to be part of?