From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Andrew Morton <akpm@linux-foundation.org>,
dri-devel@lists.freedesktop.org
Subject: Re: tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on
Date: Fri, 13 Oct 2017 17:27:59 +0200 [thread overview]
Message-ID: <7f210dc3-735e-c57e-d55a-995f950a7659@gmail.com> (raw)
In-Reply-To: <20171013100625.6c820059@gandalf.local.home>
Am 13.10.2017 um 16:06 schrieb Steven Rostedt:
> From: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
> Commit e941759c74 ("fence: dma-buf cross-device synchronization") added
> trace event fence_annotate_wait_on, but never used it. It was renamed
> to dma_fence_annotate_wait_on by commit f54d186700 ("dma-buf: Rename
> struct fence to dma_fence") but still not used. As defined trace events
> have data structures and functions created for them, it is a waste of
> memory if they are not used. Remove the unused trace event.
>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> Index: linux-trace.git/drivers/dma-buf/dma-fence.c
> ===================================================================
> --- linux-trace.git.orig/drivers/dma-buf/dma-fence.c
> +++ linux-trace.git/drivers/dma-buf/dma-fence.c
> @@ -27,7 +27,6 @@
> #define CREATE_TRACE_POINTS
> #include <trace/events/dma_fence.h>
>
> -EXPORT_TRACEPOINT_SYMBOL(dma_fence_annotate_wait_on);
> EXPORT_TRACEPOINT_SYMBOL(dma_fence_emit);
> EXPORT_TRACEPOINT_SYMBOL(dma_fence_enable_signal);
>
> Index: linux-trace.git/include/trace/events/dma_fence.h
> ===================================================================
> --- linux-trace.git.orig/include/trace/events/dma_fence.h
> +++ linux-trace.git/include/trace/events/dma_fence.h
> @@ -8,46 +8,6 @@
>
> struct dma_fence;
>
> -TRACE_EVENT(dma_fence_annotate_wait_on,
> -
> - /* fence: the fence waiting on f1, f1: the fence to be waited on. */
> - TP_PROTO(struct dma_fence *fence, struct dma_fence *f1),
> -
> - TP_ARGS(fence, f1),
> -
> - TP_STRUCT__entry(
> - __string(driver, fence->ops->get_driver_name(fence))
> - __string(timeline, fence->ops->get_timeline_name(fence))
> - __field(unsigned int, context)
> - __field(unsigned int, seqno)
> -
> - __string(waiting_driver, f1->ops->get_driver_name(f1))
> - __string(waiting_timeline, f1->ops->get_timeline_name(f1))
> - __field(unsigned int, waiting_context)
> - __field(unsigned int, waiting_seqno)
> - ),
> -
> - TP_fast_assign(
> - __assign_str(driver, fence->ops->get_driver_name(fence))
> - __assign_str(timeline, fence->ops->get_timeline_name(fence))
> - __entry->context = fence->context;
> - __entry->seqno = fence->seqno;
> -
> - __assign_str(waiting_driver, f1->ops->get_driver_name(f1))
> - __assign_str(waiting_timeline, f1->ops->get_timeline_name(f1))
> - __entry->waiting_context = f1->context;
> - __entry->waiting_seqno = f1->seqno;
> -
> - ),
> -
> - TP_printk("driver=%s timeline=%s context=%u seqno=%u " \
> - "waits on driver=%s timeline=%s context=%u seqno=%u",
> - __get_str(driver), __get_str(timeline), __entry->context,
> - __entry->seqno,
> - __get_str(waiting_driver), __get_str(waiting_timeline),
> - __entry->waiting_context, __entry->waiting_seqno)
> -);
> -
> DECLARE_EVENT_CLASS(dma_fence,
>
> TP_PROTO(struct dma_fence *fence),
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-13 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 14:06 Steven Rostedt
2017-10-13 15:27 ` Christian König [this message]
2017-10-16 9:15 ` Daniel Vetter
2017-10-16 14:37 ` Steven Rostedt
2017-10-16 15:19 ` Sumit Semwal
2017-10-16 21:16 ` Steven Rostedt
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=7f210dc3-735e-c57e-d55a-995f950a7659@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®