From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/2] fdinfo: Enable some support for GuC based client busyness
Date: Thu, 27 Apr 2023 15:47:03 -0700 [thread overview]
Message-ID: <20230427224705.2785566-1-umesh.nerlige.ramappa@intel.com> (raw)
Export context runtime into the fdinfo framework to enable per client
busyness for GuC back-end.
v2: Fix zeroed busyness values
v3: Include review comments from Ashutosh
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Umesh Nerlige Ramappa (2):
i915/pmu: Add support for total context runtime for GuC back-end
drm/i915/fdinfo: Enable fdinfo for GuC backends
drivers/gpu/drm/i915/gt/intel_context.c | 5 ++-
drivers/gpu/drm/i915/gt/intel_context.h | 2 +-
drivers/gpu/drm/i915/gt/intel_context_types.h | 2 ++
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 31 +++++++++++++++++++
drivers/gpu/drm/i915/i915_drm_client.c | 6 +---
5 files changed, 39 insertions(+), 7 deletions(-)
--
2.36.1
next reply other threads:[~2023-04-27 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 22:47 Umesh Nerlige Ramappa [this message]
2023-04-27 22:47 ` [Intel-gfx] [PATCH 1/2] i915/pmu: Add support for total context runtime for GuC back-end Umesh Nerlige Ramappa
2023-04-28 21:55 ` Dixit, Ashutosh
2023-04-27 22:47 ` [Intel-gfx] [PATCH 2/2] drm/i915/fdinfo: Enable fdinfo for GuC backends Umesh Nerlige Ramappa
2023-04-28 22:05 ` Dixit, Ashutosh
2023-04-27 23:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for fdinfo: Enable some support for GuC based client busyness (rev2) Patchwork
2023-04-27 23:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-28 4:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-04-05 0:14 [Intel-gfx] [PATCH 0/2] fdinfo: Enable some support for GuC based client busyness Umesh Nerlige Ramappa
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=20230427224705.2785566-1-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=intel-gfx@lists.freedesktop.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