From: Michael Kelley <mikelley@microsoft.com> To: Andrea Parri <parri.andrea@gmail.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org> Cc: KY Srinivasan <kys@microsoft.com>, Haiyang Zhang <haiyangz@microsoft.com>, Stephen Hemminger <sthemmin@microsoft.com>, Sasha Levin <sashal@kernel.org>, "David S . Miller" <davem@davemloft.net>, vkuznets <vkuznets@redhat.com>, Dexuan Cui <decui@microsoft.com> Subject: RE: [PATCH v2 2/3] Drivers: hv: vmbus: Enable VMBus protocol versions 4.1, 5.1 and 5.2 Date: Sat, 12 Oct 2019 13:34:43 +0000 Message-ID: <DM5PR21MB0137ACE07DCD2A6BBEC83665D7960@DM5PR21MB0137.namprd21.prod.outlook.com> (raw) In-Reply-To: <20191010154600.23875-3-parri.andrea@gmail.com> From: Andrea Parri <parri.andrea@gmail.com> Sent: Thursday, October 10, 2019 8:46 AM > > Hyper-V has added VMBus protocol versions 5.1 and 5.2 in recent release > versions. Allow Linux guests to negotiate these new protocol versions > on versions of Hyper-V that support them. While on this, also allow > guests to negotiate the VMBus protocol version 4.1 (which was missing). > > Signed-off-by: Andrea Parri <parri.andrea@gmail.com> > --- > drivers/hv/connection.c | 15 +++++++++------ > drivers/net/hyperv/netvsc.c | 6 +++--- > include/linux/hyperv.h | 8 +++++++- > net/vmw_vsock/hyperv_transport.c | 4 ++-- > 4 files changed, 21 insertions(+), 12 deletions(-) > > diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h > index c08b62dbd151f..a4f80e30b0207 100644 > --- a/include/linux/hyperv.h > +++ b/include/linux/hyperv.h > @@ -182,15 +182,21 @@ static inline u32 hv_get_avail_to_write_percent( > * 2 . 4 (Windows 8) > * 3 . 0 (Windows 8 R2) > * 4 . 0 (Windows 10) > + * 4 . 1 (Windows 10 RS3) > * 5 . 0 (Newer Windows 10) > + * 5 . 1 (Windows 10 RS4) > + * 5 . 2 (Windows Server 2019, RS5) > */ > > #define VERSION_WS2008 ((0 << 16) | (13)) > #define VERSION_WIN7 ((1 << 16) | (1)) > #define VERSION_WIN8 ((2 << 16) | (4)) > #define VERSION_WIN8_1 ((3 << 16) | (0)) > -#define VERSION_WIN10 ((4 << 16) | (0)) > +#define VERSION_WIN10_V4 ((4 << 16) | (0)) I would recommend not changing the symbol name for version 4.0. The change makes it more consistent with the later VERSION_WIN10_* symbols, but it doesn't fundamentally add any clarity and I'm not sure it's worth the churn in the other files that have to be touched. It's a judgment call, and that's just my input. > +#define VERSION_WIN10_V4_1 ((4 << 16) | (1)) > #define VERSION_WIN10_V5 ((5 << 16) | (0)) > +#define VERSION_WIN10_V5_1 ((5 << 16) | (1)) > +#define VERSION_WIN10_V5_2 ((5 << 16) | (2)) > Michael
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-10 15:45 [PATCH v2 0/3] Drivers: hv: vmbus: Miscellaneous improvements Andrea Parri 2019-10-10 15:45 ` [PATCH v2 1/3] Drivers: hv: vmbus: Introduce table of VMBus protocol versions Andrea Parri 2019-10-12 13:47 ` Michael Kelley 2019-10-14 9:52 ` Andrea Parri 2019-10-10 15:45 ` [PATCH v2 2/3] Drivers: hv: vmbus: Enable VMBus protocol versions 4.1, 5.1 and 5.2 Andrea Parri 2019-10-12 13:34 ` Michael Kelley [this message] 2019-10-14 10:09 ` Andrea Parri 2019-10-10 15:46 ` [PATCH v2 3/3] Drivers: hv: vmbus: Add module parameter to cap the VMBus version Andrea Parri
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM5PR21MB0137ACE07DCD2A6BBEC83665D7960@DM5PR21MB0137.namprd21.prod.outlook.com \ --to=mikelley@microsoft.com \ --cc=davem@davemloft.net \ --cc=decui@microsoft.com \ --cc=haiyangz@microsoft.com \ --cc=kys@microsoft.com \ --cc=linux-hyperv@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=parri.andrea@gmail.com \ --cc=sashal@kernel.org \ --cc=sthemmin@microsoft.com \ --cc=vkuznets@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Linux-HyperV Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-hyperv/0 linux-hyperv/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-hyperv linux-hyperv/ https://lore.kernel.org/linux-hyperv \ linux-hyperv@vger.kernel.org public-inbox-index linux-hyperv Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-hyperv AGPL code for this site: git clone https://public-inbox.org/public-inbox.git