From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe/execlist: Log when using execlist submission
Date: Wed, 19 Jul 2023 15:41:57 -0400 [thread overview]
Message-ID: <ZLg8hRnlu7p2VWn7@intel.com> (raw)
In-Reply-To: <20230719185707.6-1-francois.dugast@intel.com>
On Wed, Jul 19, 2023 at 06:57:07PM +0000, Francois Dugast wrote:
> Make explicit in the log that execlist submission is used to prevent from
> silently using it over GuC submission.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
> drivers/gpu/drm/xe/xe_execlist.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_execlist.c b/drivers/gpu/drm/xe/xe_execlist.c
> index 3aec37985f32..541f82387bb5 100644
> --- a/drivers/gpu/drm/xe/xe_execlist.c
> +++ b/drivers/gpu/drm/xe/xe_execlist.c
> @@ -318,9 +318,12 @@ static int execlist_engine_init(struct xe_engine *e)
> {
> struct drm_gpu_scheduler *sched;
> struct xe_execlist_engine *exl;
> + struct xe_device *xe = gt_to_xe(e->gt);
> int err;
>
> - XE_BUG_ON(xe_device_guc_submission_enabled(gt_to_xe(e->gt)));
> + XE_BUG_ON(xe_device_guc_submission_enabled(xe));
this bug_on shouldn't be here. if we have this bizarre case where we are trying
to enable execlist bug guc submission is enabled, we should put an error message
and exit gracefully, without knocking the system out. (Same for every other BUG_ONs)
But not part of this patch goal, I know...
> +
> + drm_info(&xe->drm, "Enabling execlist submission (GuC submission disabled)\n");
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> exl = kzalloc(sizeof(*exl), GFP_KERNEL);
> if (!exl)
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-19 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:57 [Intel-xe] [PATCH] drm/xe/execlist: Log when using execlist submission Francois Dugast
2023-07-19 19:07 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-07-19 19:07 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-19 19:08 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-19 19:12 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-19 19:12 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-19 19:14 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-19 19:41 ` Rodrigo Vivi [this message]
2023-07-19 19:49 ` [Intel-xe] ○ CI.BAT: info " 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=ZLg8hRnlu7p2VWn7@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.