public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dexuan Cui <decui@microsoft•com>
To: gregkh@linuxfoundation•org, davem@davemloft•net,
	stephen@networkplumber•org, netdev@vger•kernel.org,
	linux-kernel@vger•kernel.org,
	driverdev-devel@linuxdriverproject•org, olaf@aepfle•de,
	apw@canonical•com, jasowang@redhat•com, kys@microsoft•com,
	vkuznets@redhat•com
Cc: pebolle@tiscali•nl, dan.carpenter@oracle•com, stefanha@redhat•com
Subject: [PATCH V6 2/8] Drivers: hv: vmbus: define the new offer type for Hyper-V socket (hvsock)
Date: Tue, 26 Jan 2016 01:44:15 -0800	[thread overview]
Message-ID: <1453801455-3284-1-git-send-email-decui@microsoft.com> (raw)

A helper function is also added.

Signed-off-by: Dexuan Cui <decui@microsoft•com>
---
 include/linux/hyperv.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index e4867a7..c0eddd7 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -235,6 +235,7 @@ struct vmbus_channel_offer {
 #define VMBUS_CHANNEL_LOOPBACK_OFFER			0x100
 #define VMBUS_CHANNEL_PARENT_OFFER			0x200
 #define VMBUS_CHANNEL_REQUEST_MONITORED_NOTIFICATION	0x400
+#define VMBUS_CHANNEL_TLNPI_PROVIDER_OFFER		0x2000
 
 struct vmpacket_descriptor {
 	u16 type;
@@ -769,6 +770,12 @@ struct vmbus_channel {
 	enum hv_signal_policy  signal_policy;
 };
 
+static inline bool is_hvsock_channel(const struct vmbus_channel *c)
+{
+	return !!(c->offermsg.offer.chn_flags &
+		  VMBUS_CHANNEL_TLNPI_PROVIDER_OFFER);
+}
+
 static inline void set_channel_signal_state(struct vmbus_channel *c,
 					    enum hv_signal_policy policy)
 {
-- 
2.1.0

                 reply	other threads:[~2016-01-26  9:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly 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=1453801455-3284-1-git-send-email-decui@microsoft.com \
    --to=decui@microsoft$(echo .)com \
    --cc=apw@canonical$(echo .)com \
    --cc=dan.carpenter@oracle$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=driverdev-devel@linuxdriverproject$(echo .)org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=jasowang@redhat$(echo .)com \
    --cc=kys@microsoft$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=olaf@aepfle$(echo .)de \
    --cc=pebolle@tiscali$(echo .)nl \
    --cc=stefanha@redhat$(echo .)com \
    --cc=stephen@networkplumber$(echo .)org \
    --cc=vkuznets@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox