From: "Michel Dänzer" <michel@daenzer.net>
To: Vipin <vj358@nyu.edu>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Empty /proc/dri/0/bufs queues -
Date: Sat, 13 Aug 2011 18:34:54 +0200 [thread overview]
Message-ID: <1313253294.15614.45.camel@thor.local> (raw)
In-Reply-To: <4E4444E7.6040008@nyu.edu>
On Don, 2011-08-11 at 17:08 -0400, Vipin wrote:
>
> *I think the first message got discarded, posting a second one*
It didn't, maybe it was delayed via the moderation queue.
> Empty /proc/dri/0 bufs, queues files
> Is this an expected behavior ?
Yes, these aren't relevant with KMS.
> /sys/kernel/debug/dri/
>
> There are two directories 0 & 64, what does the 64 entry signify ?
It corresponds to the control device node /dev/dri/controlD64 . There
are legacy/control/render nodes, but I don't remember the details about
the distinction.
> The contents of /sys/kernel/debug/dri/0 contains 15 radeon_ib_00xx
> Does this mean, the card has 15 indirect buffers ?
The card imposes no restrictions on the number of indirect buffers (IBs)
that can be allocated. The radeon driver pre-allocates 16 IBs for
dispatching commands to the GPU.
> Also, does this interface shows me the ringbuffer data like i915.
Yes.
> The kernel log shows entries like these (massive amounts)
> Aug 11 13:19:01 gilubuntu1 kernel: [ 4251.705377] [drm:drm_ioctl],
> pid=1544, cmd=0xc0086464, nr=0x64, dev 0xe200, auth=1
> Aug 11 13:19:01 gilubuntu1 kernel: [ 4251.705394] [drm:r600_irq_set],
> r600_irq_set: sw int
>
> Shouldn't it have other debug entries other than these two ?
It should, they might be drowned by these two. Or maybe you need to
enable more debugging messages e.g. with drm.debug=0x3 or =0x7.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2011-08-13 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 21:08 Empty /proc/dri/0/bufs queues - Vipin
2011-08-13 16:34 ` Michel Dänzer [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=1313253294.15614.45.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=vj358@nyu.edu \
/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