[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221207163506.GA2010@lst.de>
Date: Wed, 7 Dec 2022 17:35:06 +0100
From: Christoph Hellwig <hch@....de>
To: Max Gurtovoy <mgurtovoy@...dia.com>
Cc: Christoph Hellwig <hch@....de>, Jason Gunthorpe <jgg@...pe.ca>,
Lei Rao <lei.rao@...el.com>, kbusch@...nel.org, axboe@...com,
kch@...dia.com, sagi@...mberg.me, alex.williamson@...hat.com,
cohuck@...hat.com, yishaih@...dia.com,
shameerali.kolothum.thodi@...wei.com, kevin.tian@...el.com,
mjrosato@...ux.ibm.com, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, kvm@...r.kernel.org,
eddie.dong@...el.com, yadong.li@...el.com, yi.l.liu@...el.com,
Konrad.wilk@...cle.com, stephen@...eticom.com, hang.yuan@...el.com
Subject: Re: [RFC PATCH 1/5] nvme-pci: add function nvme_submit_vf_cmd to
issue admin commands for VF driver.
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?
Powered by blists - more mailing lists