Messages in this thread | | | From | Dexuan Cui <> | Subject | RE: [PATCH 0/2] Drivers: hv: vmbus: Miscellaneous improvements | Date | Mon, 7 Oct 2019 17:41:10 +0000 |
| |
> From: linux-hyperv-owner@vger.kernel.org > <linux-hyperv-owner@vger.kernel.org> On Behalf Of Andrea Parri > Sent: Monday, October 7, 2019 9:31 AM > > Hi all, > > The patchset: > > - simplifies/refactors the VMBus negotiation code by introducing > the table of VMBus protocol versions (patch 1/2), > > - enables VMBus protocol versions 5.1 and 5.2 (patch 2/2). > > Thanks, > Andrea > > Andrea Parri (2): > Drivers: hv: vmbus: Introduce table of VMBus protocol versions > Drivers: hv: vmbus: Enable VMBus protocol versions 5.1 and 5.2
Should we add a module parameter to allow the user to specify a lower protocol version, when the VM runs on the latest host?
This can be useful for testing and debugging purpose: the variable "vmbus_proto_version" is referenced by the vmbus driver itself and some VSC drivers: if we always use the latest available proto version, some code paths can not be tested on the latest hosts.
Thanks, -- Dexuan
| |