summaryrefslogtreecommitdiff
path: root/datapath-windows/ovsext/TunnelIntf.h
diff options
context:
space:
mode:
authorSorin Vinturis <svinturis@cloudbasesolutions.com>2015-04-29 12:58:16 +0000
committerGurucharan Shetty <gshetty@nicira.com>2015-04-29 07:26:56 -0700
commit9719aee5c7bf4d3b99a0b25eecf86ea0eef652e8 (patch)
tree9f5322aed039c19adf6d56de255cdbda7adc111e /datapath-windows/ovsext/TunnelIntf.h
parent5c62a855c7bb24424cbe7ec48ecf2f128db8b102 (diff)
downloadopenvswitch-9719aee5c7bf4d3b99a0b25eecf86ea0eef652e8.tar.gz
datapath-windows: Enable extension after rrestart
The extension failed to be activated during booting due to the failure to initialize tunnel filter. This happened because the Base Filtering Engine (BFE) is not started and no session to the engine could be acquired. The solution for this was to registered a BFE notification callback that is called whenever the BFE's state changes. Only if the BFE's state is running the tunnel filter is initialized. Signed-off-by: Sorin Vinturis <svinturis@cloudbasesolutions.com> Reported-by: Sorin Vinturis <svinturis@cloudbasesolutions.com> Reported-at: https://github.com/openvswitch/ovs-issues/issues/77 Acked-by: Eitan Eliahu <eliahue@vmware.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
Diffstat (limited to 'datapath-windows/ovsext/TunnelIntf.h')
-rw-r--r--datapath-windows/ovsext/TunnelIntf.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/datapath-windows/ovsext/TunnelIntf.h b/datapath-windows/ovsext/TunnelIntf.h
index 728a53f7f..82a51459a 100644
--- a/datapath-windows/ovsext/TunnelIntf.h
+++ b/datapath-windows/ovsext/TunnelIntf.h
@@ -18,9 +18,9 @@
#define __TUNNEL_INTF_H_ 1
/* Tunnel callout driver load/unload functions */
-NTSTATUS OvsTunnelFilterInitialize(PDRIVER_OBJECT driverObject);
+NTSTATUS OvsInitTunnelFilter(PDRIVER_OBJECT driverObject, PVOID deviceObject);
-VOID OvsTunnelFilterUninitialize(PDRIVER_OBJECT driverObject);
+VOID OvsUninitTunnelFilter(PDRIVER_OBJECT driverObject);
VOID OvsRegisterSystemProvider(PVOID deviceObject);