Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-xe@lists.freedesktop.org,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Cc: jose.souza@intel.com
Subject: [PATCH 0/2] Fixes for MI_REPORT_PERF_COUNT
Date: Wed, 18 Dec 2024 16:23:38 -0800	[thread overview]
Message-ID: <20241219002340.13230-1-umesh.nerlige.ramappa@intel.com> (raw)

OA programming sequence for query mode or MI_REPORT_PERF_COUNT requires
modifying some HW registers in the same hw context as the user exec
queue. User passes the exec_queue to the OA interface and OA
implementation submits an MI_LOAD_REGISTER_IMM to this queue to modify
the registers.

The OA implementation submits a batch mapped in GGTT to the user exec
queue and hence, some plumbing is added into relevant code to enable
that (as per suggestions from Matthew Brost).

v2: review rework
v3:
- review rework
- original patches squashed for porting to stable
- code cleanup

opens:
- Should the cleanup patch be squashed as well and sent to stable? I have kept
  it separate hoping the build does not complain about dead code!!
- Applying these patches to stable is not clean since there is a dependency on
  another patch - "drm/xe: Force write completion of MI_STORE_DATA_IMM". Not
  sure if dependent patches need to be sent to stable as well.

Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Umesh Nerlige Ramappa (2):
  xe/oa: Fix query mode of operation for OAR/OAC
  xe/oa: Drop the unused logic to parse context image

 drivers/gpu/drm/xe/xe_oa.c              | 223 +++++-------------------
 drivers/gpu/drm/xe/xe_oa_types.h        |   3 -
 drivers/gpu/drm/xe/xe_ring_ops.c        |   5 +-
 drivers/gpu/drm/xe/xe_sched_job_types.h |   2 +
 4 files changed, 53 insertions(+), 180 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-12-19  0:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  0:23 Umesh Nerlige Ramappa [this message]
2024-12-19  0:23 ` [PATCH 1/2] xe/oa: Fix query mode of operation for OAR/OAC Umesh Nerlige Ramappa
2024-12-19 23:15   ` Dixit, Ashutosh
2024-12-20  0:19     ` Umesh Nerlige Ramappa
2024-12-19  0:23 ` [PATCH 2/2] xe/oa: Drop the unused logic to parse context image Umesh Nerlige Ramappa
2024-12-19  2:31 ` ✓ CI.Patch_applied: success for Fixes for MI_REPORT_PERF_COUNT (rev3) Patchwork
2024-12-19  2:31 ` ✓ CI.checkpatch: " Patchwork
2024-12-19  2:32 ` ✓ CI.KUnit: " Patchwork
2024-12-19  2:50 ` ✓ CI.Build: " Patchwork
2024-12-19  2:53 ` ✓ CI.Hooks: " Patchwork
2024-12-19  2:54 ` ✓ CI.checksparse: " Patchwork
2024-12-19  3:27 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-19 23:44 ` ✗ Xe.CI.Full: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-12-17  0:58 [PATCH 0/2] Fixes for MI_REPORT_PERF_COUNT Umesh Nerlige Ramappa
2024-12-17 17:05 ` Souza, Jose
2024-12-17 17:13   ` Souza, Jose
2024-12-17 18:51     ` Umesh Nerlige Ramappa
2024-11-27  0:31 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=20241219002340.13230-1-umesh.nerlige.ramappa@intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@intel.com \
    /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