[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR21MB013736C1459A260E9D6E9A31D7930@DM5PR21MB0137.namprd21.prod.outlook.com>
Date: Tue, 15 Oct 2019 13:15:32 +0000
From: Michael Kelley <mikelley@...rosoft.com>
To: Andrea Parri <parri.andrea@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
CC: KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Sasha Levin <sashal@...nel.org>,
vkuznets <vkuznets@...hat.com>, Dexuan Cui <decui@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>
Subject: RE: [PATCH v3 3/3] Drivers: hv: vmbus: Add module parameter to cap
the VMBus version
From: Andrea Parri <parri.andrea@...il.com> Sent: Tuesday, October 15, 2019 4:47 AM
>
> Currently, Linux guests negotiate the VMBus version with Hyper-V
> and use the highest available VMBus version they can connect to.
> This has some drawbacks: by using the highest available version,
> certain code paths are never executed and can not be tested when
> the guest runs on the newest host.
>
> Add the module parameter "max_version", to upper-bound the VMBus
> versions guests can negotiate.
>
> Suggested-by: Dexuan Cui <decui@...rosoft.com>
> Signed-off-by: Andrea Parri <parri.andrea@...il.com>
> ---
> drivers/hv/connection.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
Reviewed-by: Michael Kelley <mikelley@...rosoft.com>
Powered by blists - more mailing lists