Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: FlightlessMango <flightlessmangoyt@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Martin Peres <martin.peres@mupuf.org>
Subject: [Intel-gfx] [OA][RFC] Exposing low-resolution engine business via sysfs
Date: Thu, 12 Jan 2023 08:50:23 +0100	[thread overview]
Message-ID: <65afb3a4-bdc1-04a8-a2ac-6c561cddd710@gmail.com> (raw)

Hi,

I am the developer of MangoHud[1], a Vulkan and OpenGL overlay for 
monitoring FPS / temperatures / CPU/GPU load and more.

I would like to add support for i915 (and xe in the future) but I am 
currently unable to do this easily because not everything I need is 
exposed directly to non-root users. Namely:

  * Engine business (RCS)
  * CPU, iGPU and dGPU power usage
  * IMC bandwith (nice to have but not mandatory)

This is a problem because it would require us to ship a setuid binary to 
poll these metrics for the overlay (we can't run games as root).

For your information, this is Intel-specific as AMD and NVIDIA are 
exposing these values directly. I understand the security concerns, but 
we are not asking for super precise information (1% accuracy is perfect).

Can we work together on this, what are your thoughts?

Thanks for your consideration.

//Simon Hallsten

[1] https://github.com/flightlessmango/MangoHud




             reply	other threads:[~2023-01-12  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  7:50 FlightlessMango [this message]
2023-01-12  8:55 ` [Intel-gfx] [OA][RFC] Exposing low-resolution engine business via sysfs Tvrtko Ursulin

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=65afb3a4-bdc1-04a8-a2ac-6c561cddd710@gmail.com \
    --to=flightlessmangoyt@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=martin.peres@mupuf.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