From: Gustavo Padovan <gustavo@padovan.org>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH] dma-buf: fence debugging
Date: Fri, 31 Mar 2017 18:12:46 +0200 [thread overview]
Message-ID: <20170331161246.GA2252@joana> (raw)
In-Reply-To: <E1cttMI-00068z-3X@rmk-PC.armlinux.org.uk>
Hi Russell,
2017-03-31 Russell King <rmk+kernel@arm.linux.org.uk>:
> Add debugfs output to report shared and exclusive fences on a dma_buf
> object. This produces output such as:
>
> Dma-buf Objects:
> size flags mode count exp_name
> 08294400 00000000 00000005 00000005 drm
> Exclusive fence: etnaviv 134000.gpu signalled
> Attached Devices:
> gpu-subsystem
> Total 1 devices attached
>
>
> Total 1 objects, 8294400 bytes
>
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
> drivers/dma-buf/dma-buf.c | 34 +++++++++++++++++++++++++++++++++-
> 1 file changed, 33 insertions(+), 1 deletions(-)
Applied to to drm-misc-next.
>
> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> index 0007b792827b..f72aaacbe023 100644
> --- a/drivers/dma-buf/dma-buf.c
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -1059,7 +1059,11 @@ static int dma_buf_debug_show(struct seq_file *s, void *unused)
> int ret;
> struct dma_buf *buf_obj;
> struct dma_buf_attachment *attach_obj;
> - int count = 0, attach_count;
> + struct reservation_object *robj;
> + struct reservation_object_list *fobj;
> + struct dma_fence *fence;
> + unsigned seq;
Our maintainer tools warned about this line, so I made it "unsigned
int"
Gustavo
prev parent reply other threads:[~2017-03-31 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 10:00 [PATCH] dma-buf: fence debugging Russell King
2017-03-31 12:06 ` Christian König
2017-03-31 12:06 ` Christian König
2017-03-31 16:12 ` Gustavo Padovan [this message]
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=20170331161246.GA2252@joana \
--to=gustavo@padovan.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.