Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Nerlige Ramappa, Umesh" <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH 0/2] Disallow OA from being enabled on active exec_queue's
Date: Mon, 11 Nov 2024 14:31:30 +0000	[thread overview]
Message-ID: <d0c25af29401371ae71086e48ae509a8c50c3199.camel@intel.com> (raw)
In-Reply-To: <20241108230602.2984959-1-ashutosh.dixit@intel.com>

There is any down side in having OAC_CONTEXT_ENABLE set in all contexts?
I remember reading in bspec that it should be part of the golden context.

On Fri, 2024-11-08 at 15:05 -0800, Ashutosh Dixit wrote:
> Ashutosh Dixit (2):
>   drm/xe/oa: Disallow OA from being enabled on active exec_queue's
>   drm/xe/oa: Allow subsequent OA streams to be opened on an exec_queue
> 
>  drivers/gpu/drm/xe/xe_exec_queue_types.h |  2 ++
>  drivers/gpu/drm/xe/xe_guc_submit.c       |  2 +-
>  drivers/gpu/drm/xe/xe_guc_submit.h       |  1 +
>  drivers/gpu/drm/xe/xe_oa.c               | 15 +++++++++++++++
>  4 files changed, 19 insertions(+), 1 deletion(-)
> 


      parent reply	other threads:[~2024-11-11 14:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 23:05 [PATCH 0/2] Disallow OA from being enabled on active exec_queue's Ashutosh Dixit
2024-11-08 23:06 ` [PATCH 1/2] drm/xe/oa: " Ashutosh Dixit
2024-11-08 23:14   ` Matthew Brost
2024-11-19  1:35     ` Dixit, Ashutosh
2024-11-08 23:38   ` Cavitt, Jonathan
2024-11-08 23:06 ` [PATCH 2/2] drm/xe/oa: Allow subsequent OA streams to be opened on an exec_queue Ashutosh Dixit
2024-11-08 23:42   ` Cavitt, Jonathan
2024-11-19  1:36     ` Dixit, Ashutosh
2024-11-08 23:11 ` ✓ CI.Patch_applied: success for Disallow OA from being enabled on active exec_queue's Patchwork
2024-11-08 23:11 ` ✓ CI.checkpatch: " Patchwork
2024-11-08 23:12 ` ✓ CI.KUnit: " Patchwork
2024-11-08 23:24 ` ✓ CI.Build: " Patchwork
2024-11-08 23:26 ` ✓ CI.Hooks: " Patchwork
2024-11-08 23:28 ` ✓ CI.checksparse: " Patchwork
2024-11-08 23:45 ` ✓ CI.BAT: " Patchwork
2024-11-10  2:29 ` ✗ CI.FULL: failure " Patchwork
2024-11-11 14:31 ` Souza, Jose [this message]

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