Commit c0b0ce6c authored by Takashi Sakamoto's avatar Takashi Sakamoto

firewire: core: add tracepoints events for flushing of isochronous context

It is helpful to trace the flushing of isochronous context when the core
function is requested them by both in-kernel unit drivers and userspace
applications.

This commit adds some tracepoints events for the aim.

Link: https://lore.kernel.org/r/20240623220859.851685-5-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
parent 4e64210f
......@@ -197,6 +197,10 @@ EXPORT_SYMBOL(fw_iso_context_queue);
void fw_iso_context_queue_flush(struct fw_iso_context *ctx)
{
trace_isoc_outbound_flush(ctx);
trace_isoc_inbound_single_flush(ctx);
trace_isoc_inbound_multiple_flush(ctx);
ctx->card->driver->flush_queue_iso(ctx);
}
EXPORT_SYMBOL(fw_iso_context_queue_flush);
......
......@@ -670,6 +670,42 @@ DEFINE_EVENT_CONDITION(isoc_stop_template, isoc_inbound_multiple_stop,
TP_CONDITION(ctx->type == FW_ISO_CONTEXT_RECEIVE_MULTICHANNEL)
);
DECLARE_EVENT_CLASS(isoc_flush_template,
TP_PROTO(const struct fw_iso_context *ctx),
TP_ARGS(ctx),
TP_STRUCT__entry(
__field(u64, context)
__field(u8, card_index)
),
TP_fast_assign(
__entry->context = (uintptr_t)ctx;
__entry->card_index = ctx->card->index;
),
TP_printk(
"context=0x%llx card_index=%u",
__entry->context,
__entry->card_index
)
);
DEFINE_EVENT_CONDITION(isoc_flush_template, isoc_outbound_flush,
TP_PROTO(const struct fw_iso_context *ctx),
TP_ARGS(ctx),
TP_CONDITION(ctx->type == FW_ISO_CONTEXT_TRANSMIT)
);
DEFINE_EVENT_CONDITION(isoc_flush_template, isoc_inbound_single_flush,
TP_PROTO(const struct fw_iso_context *ctx),
TP_ARGS(ctx),
TP_CONDITION(ctx->type == FW_ISO_CONTEXT_RECEIVE)
);
DEFINE_EVENT_CONDITION(isoc_flush_template, isoc_inbound_multiple_flush,
TP_PROTO(const struct fw_iso_context *ctx),
TP_ARGS(ctx),
TP_CONDITION(ctx->type == FW_ISO_CONTEXT_RECEIVE_MULTICHANNEL)
);
#undef QUADLET_SIZE
#endif // _FIREWIRE_TRACE_EVENT_H
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment