From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>
Subject: Re: [PATCH 0/2] Fixes for MI_REPORT_PERF_COUNT
Date: Tue, 17 Dec 2024 10:51:41 -0800 [thread overview]
Message-ID: <Z2HIPT4fZPnpsD58@orsosgc001> (raw)
In-Reply-To: <fd6204d5194f31a7fd4592849a1ba5e8cf02d26a.camel@intel.com>
On Tue, Dec 17, 2024 at 09:13:12AM -0800, Souza, Jose wrote:
>On Tue, 2024-12-17 at 17:05 +0000, Souza, Jose wrote:
>> On Mon, 2024-12-16 at 16:58 -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
>>
>> This series fixes GPU hang happening when close OA stream.
>>
>> Tested-by: José Roberto de Souza <jose.souza@intel.com>
>
>Ah can you add a Fixes tag to 8135f1c09dd2eecee7cb637f7ec9a29e57300eb8 ?
>Would be nice to get this patch backported to older kernel releases.
Sure, will do. Thanks for testing it out.
Umesh
>
>>
>> >
>> > Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>> >
>> > Umesh Nerlige Ramappa (2):
>> > xe: Allow a GGTT mapped batch to be submitted to user exec queue
>> > xe/oa: Use MI_LOAD_REGISTER_IMMEDIATE to enable OAR/OAC
>> >
>> > drivers/gpu/drm/xe/xe_oa.c | 71 ++++++++++++++++++-------
>> > drivers/gpu/drm/xe/xe_ring_ops.c | 5 +-
>> > drivers/gpu/drm/xe/xe_sched_job_types.h | 2 +
>> > 3 files changed, 57 insertions(+), 21 deletions(-)
>> >
>>
>
next prev parent reply other threads:[~2024-12-17 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 0:58 [PATCH 0/2] Fixes for MI_REPORT_PERF_COUNT Umesh Nerlige Ramappa
2024-12-17 0:58 ` [PATCH 1/2] xe: Allow a GGTT mapped batch to be submitted to user exec queue Umesh Nerlige Ramappa
2024-12-17 0:58 ` [PATCH 2/2] xe/oa: Use MI_LOAD_REGISTER_IMMEDIATE to enable OAR/OAC Umesh Nerlige Ramappa
2024-12-17 1:26 ` Matthew Brost
2024-12-18 3:32 ` Dixit, Ashutosh
2024-12-17 2:30 ` ✓ CI.Patch_applied: success for Fixes for MI_REPORT_PERF_COUNT (rev2) Patchwork
2024-12-17 2:30 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-17 2:32 ` ✓ CI.KUnit: success " Patchwork
2024-12-17 2:50 ` ✓ CI.Build: " Patchwork
2024-12-17 2:52 ` ✓ CI.Hooks: " Patchwork
2024-12-17 2:53 ` ✓ CI.checksparse: " Patchwork
2024-12-17 5:40 ` ✓ CI.BAT: " Patchwork
2024-12-17 17:05 ` [PATCH 0/2] Fixes for MI_REPORT_PERF_COUNT Souza, Jose
2024-12-17 17:13 ` Souza, Jose
2024-12-17 18:51 ` Umesh Nerlige Ramappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-19 0:23 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=Z2HIPT4fZPnpsD58@orsosgc001 \
--to=umesh.nerlige.ramappa@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=matthew.brost@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