mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-27 13:05:03 +08:00
c4ab7b56be
This makes openvswitch module use the event tracing framework
to log the upcall interface and action execution pipeline. When
using openvswitch as the packet forwarding engine, some types of
debugging are made possible simply by using the ovs-vswitchd's
ofproto/trace command. However, such a command has some
limitations:
1. When trying to trace packets that go through the CT action,
the state of the packet can't be determined, and probably
would be potentially wrong.
2. Deducing problem packets can sometimes be difficult as well
even if many of the flows are known
3. It's possible to use the openvswitch module even without
the ovs-vswitchd (although, not common use).
Introduce the event tracing points here to make it possible for
working through these problems in kernel space. The style is
copied from the mac80211 driver-trace / trace code for
consistency - this creates some checkpatch splats, but the
official 'guide' for adding tracepoints, as well as the existing
examples all add the same splats so it seems acceptable.
Signed-off-by: Aaron Conole <aconole@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
30 lines
554 B
Makefile
30 lines
554 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# Makefile for Open vSwitch.
|
|
#
|
|
|
|
obj-$(CONFIG_OPENVSWITCH) += openvswitch.o
|
|
|
|
openvswitch-y := \
|
|
actions.o \
|
|
datapath.o \
|
|
dp_notify.o \
|
|
flow.o \
|
|
flow_netlink.o \
|
|
flow_table.o \
|
|
meter.o \
|
|
openvswitch_trace.o \
|
|
vport.o \
|
|
vport-internal_dev.o \
|
|
vport-netdev.o
|
|
|
|
ifneq ($(CONFIG_NF_CONNTRACK),)
|
|
openvswitch-y += conntrack.o
|
|
endif
|
|
|
|
obj-$(CONFIG_OPENVSWITCH_VXLAN)+= vport-vxlan.o
|
|
obj-$(CONFIG_OPENVSWITCH_GENEVE)+= vport-geneve.o
|
|
obj-$(CONFIG_OPENVSWITCH_GRE) += vport-gre.o
|
|
|
|
CFLAGS_openvswitch_trace.o = -I$(src)
|