Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Dixit,  Ashutosh" <ashutosh.dixit@intel.com>
Subject: Re: [PATCH v5 0/2] Fixes for MI_REPORT_PERF_COUNT
Date: Fri, 20 Dec 2024 16:35:15 -0800	[thread overview]
Message-ID: <Z2YNQ/LTFMTCRQBZ@orsosgc001> (raw)
In-Reply-To: <d4f89ead15c16e232681fcf96fb1a0669b0d2249.camel@intel.com>

On Fri, Dec 20, 2024 at 11:54:04AM -0800, Souza, Jose wrote:
>On Fri, 2024-12-20 at 09:19 -0800, Umesh Nerlige Ramappa wrote:
>> 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
>>
>> v4:
>> - review rework/fixes
>>
>> v5:
>> - minor review rework/fixes
>
>v5 fixed the oops that I got in v4 and also fixed the GPU hang when closing OA stream.

Thanks a lot for catching that in v4 and ensuring v5 works.

Regards,
Umesh
>
>>
>> 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              | 224 +++++-------------------
>>  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, 51 insertions(+), 183 deletions(-)
>>
>

  parent reply	other threads:[~2024-12-21  0:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:19 [PATCH v5 0/2] Fixes for MI_REPORT_PERF_COUNT Umesh Nerlige Ramappa
2024-12-20 17:19 ` [PATCH v5 1/2] xe/oa: Fix query mode of operation for OAR/OAC Umesh Nerlige Ramappa
2024-12-20 18:08   ` Cavitt, Jonathan
2024-12-20 18:24     ` Dixit, Ashutosh
2024-12-20 18:51       ` Cavitt, Jonathan
2024-12-20 22:00     ` Dixit, Ashutosh
2024-12-20 17:19 ` [PATCH v5 2/2] xe/oa: Drop the unused logic to parse context image Umesh Nerlige Ramappa
2024-12-20 18:09   ` Cavitt, Jonathan
2024-12-20 18:03 ` ✓ CI.Patch_applied: success for Fixes for MI_REPORT_PERF_COUNT (rev5) Patchwork
2024-12-20 18:03 ` ✓ CI.checkpatch: " Patchwork
2024-12-20 18:05 ` ✓ CI.KUnit: " Patchwork
2024-12-20 18:23 ` ✓ CI.Build: " Patchwork
2024-12-20 18:25 ` ✓ CI.Hooks: " Patchwork
2024-12-20 18:27 ` ✓ CI.checksparse: " Patchwork
2024-12-20 18:59 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-20 19:54 ` [PATCH v5 0/2] Fixes for MI_REPORT_PERF_COUNT Souza, Jose
2024-12-20 20:05   ` Dixit, Ashutosh
2024-12-21  0:35   ` Umesh Nerlige Ramappa [this message]
2024-12-21 22:41 ` ✗ Xe.CI.Full: failure for Fixes for MI_REPORT_PERF_COUNT (rev5) Patchwork

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=Z2YNQ/LTFMTCRQBZ@orsosgc001 \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@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