Re: [RFC PATCH 5/5] nvme-vfio: Add a document for the NVMe device

Chaitanya Kulkarni
2022-12-08T05:39:17Z

Keith,

On 12/7/22 16:03, Keith Busch wrote:
> On Wed, Dec 07, 2022 at 10:54:25PM +0000, Chaitanya Kulkarni wrote:
>> This is only reference implementation. The process of the
>> standardization of the NVMe Live Migration is will take of these
>> opcodes and anything Vendor specific present in this series.
>>
>> It is very important to get some feedback on this to help the
>> standardization in any way.
>
> We have the NVMe TWG, and live-migration is already active with TPAR4195. Why
> is anyone thinking a Linux mailing list is the appropriate forum to discuss
> standardizing an OS agnositic feature at this point? Your vfio APIs and vendor
> specific hijacks are premature implementation details at this point.

hmmm but it does have another subsystem than NVMe: VFIO and we don't
know how it will affect TP or not. There is no intention to
upstream vendor specific implementation as stated explicitly in
the cover-letter.

Can you please let us know what is the right way in this case to
get a feedback from both subsystems NVMe and VFIO ?

I think similar attempt is been done as RFC [1]. Aren't RFCs
supposed to be posted to get more clarification either way ?
and if it is soo premature in a way that is not even worth
generating productive discussion then we can simply let
authors know.

-ck

[1]