From: Rhyland Klein <rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Exposing GPU information for userspace processes
Date: Tue, 9 Jul 2013 17:45:55 -0400 [thread overview]
Message-ID: <51DC8493.9090405@nvidia.com> (raw)
We are currently looking into exporting some information from the linux
kernel to userspace about the GPU. This information is specific per
board as the data can vary depending on the fuses burnt on the board.
Right now we are leaning towards adding sysfs properties to our existing
nodes to share this information.
Before we write up the patches and update our userspace apps to check
the new locations, we wanted to make sure there wasn't a more
accepted/proper way to export information already.
Right now for instance we want to export a property to say how many
pixel pipes there are. This could then be exported in something like:
/sys/bus/platform/drivers/gr3d/54180000.gr3d/num_pixel_pipes
Is this the best approach to take right now or is there another way we
should export this and similar HW specific information?
Thanks,
Rhyland
--
nvpublic
next reply other threads:[~2013-07-09 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 21:45 Rhyland Klein [this message]
[not found] ` <51DC8493.9090405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-07-10 6:01 ` Exposing GPU information for userspace processes Dave Airlie
[not found] ` <CAPM=9tyCTF_+Z0S0+TKxio94LCRpJeWJ6U2EcozUj8tjmMESNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-10 6:09 ` Daniel Vetter
[not found] ` <20130710060949.GG18285-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2013-07-10 16:11 ` Rhyland Klein
2013-07-17 5:40 ` Thierry Reding
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=51DC8493.9090405@nvidia.com \
--to=rklein-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).