mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-24 15:01:13 +07:00
a5448fdc46
This patch introduces target-side request tracing. As Christoph suggested, the trace would not be in a core or module to avoid disadvantages like cache miss: http://lists.infradead.org/pipermail/linux-nvme/2019-June/024721.html The target-side trace code is entirely based on the Johannes's trace code from the host side. It has lots of codes duplicated, but it would be better than having advantages mentioned above. It also traces not only fabrics commands, but also nvme normal commands. Once the codes to be shared gets bigger, then we can make it common as suggsted. This also removed the create_sq and create_cq trace parsing functions because it will be done by the connect fabrics command. Example: echo 1 > /sys/kernel/debug/tracing/event/nvmet/nvmet_req_init/enable echo 1 > /sys/kernel/debug/tracing/event/nvmet/nvmet_req_complete/enable cat /sys/kernel/debug/tracing/trace Signed-off-by: Minwoo Im <minwoo.im.dev@gmail.com> [hch: fixed the symbol namespace and a an endianess conversion] Signed-off-by: Christoph Hellwig <hch@lst.de>
20 lines
583 B
Makefile
20 lines
583 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
ccflags-y += -I$(src)
|
|
|
|
obj-$(CONFIG_NVME_TARGET) += nvmet.o
|
|
obj-$(CONFIG_NVME_TARGET_LOOP) += nvme-loop.o
|
|
obj-$(CONFIG_NVME_TARGET_RDMA) += nvmet-rdma.o
|
|
obj-$(CONFIG_NVME_TARGET_FC) += nvmet-fc.o
|
|
obj-$(CONFIG_NVME_TARGET_FCLOOP) += nvme-fcloop.o
|
|
obj-$(CONFIG_NVME_TARGET_TCP) += nvmet-tcp.o
|
|
|
|
nvmet-y += core.o configfs.o admin-cmd.o fabrics-cmd.o \
|
|
discovery.o io-cmd-file.o io-cmd-bdev.o
|
|
nvme-loop-y += loop.o
|
|
nvmet-rdma-y += rdma.o
|
|
nvmet-fc-y += fc.o
|
|
nvme-fcloop-y += fcloop.o
|
|
nvmet-tcp-y += tcp.o
|
|
nvmet-$(CONFIG_TRACING) += trace.o
|