OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [PATCH V2 6/6] virtio-pci: implement dirty page tracking


> From: Zhu, Lingshan <lingshan.zhu@intel.com>
> Sent: Monday, November 6, 2023 3:04 PM

> So, please no pass-through discussion anymore.

If you comment like this, nothing can progress.

What you are implying with above language is: 
"hey a virtio can do live migration ONLY by creating vdpa device on top of ALREADY virtio device, and you get another virtio device by running through 3 layers of stack you get virtio device on other side!".

Then for sure, I disagree to it for 100% for such a single-minded design.

At least I am trying to propose if a solution can work for generic passthrough where least amount of hypervisor mediation is done.

And an extension where hypervisor has choice to more medication layers as it finds suitable.
And if there are technical issues, may be two different interfaces or more admin commands needed for two modes.
The idea is to attempt to converge and discuss those details, not the opposite.

Your above comment shows a clear sign of non-collaboration to make both mode works.
At one point I may probably stop responding to your comments that repeatedly says:

"Go read QEMU code, Do you know what is PASID?, Do you know num_queues, Go read PCI spec"...

Taking deep breath now to do some productive work in TC...


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]