Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: <fei.yang@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: <matthew.d.roper@intel.com>
Subject: Re: [PATCH 1/1] drm/xe: enable lite restore
Date: Thu, 10 Oct 2024 10:32:31 -0700	[thread overview]
Message-ID: <fb530ce7-17de-4600-a045-c2b91a66c5ae@intel.com> (raw)
In-Reply-To: <20241010173142.425498-2-fei.yang@intel.com>

On 10/10/2024 10:31, fei.yang@intel.com wrote:
> From: Fei Yang <fei.yang@intel.com>
>
> The lite restore feature is supposed to be enabled by default.
>
> Signed-off-by: Fei Yang <fei.yang@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>

> ---
>   drivers/gpu/drm/xe/xe_guc.c      | 2 +-
>   drivers/gpu/drm/xe/xe_guc_fwif.h | 1 +
>   2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 8570b1218287..fed30f2872f7 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -70,7 +70,7 @@ static u32 guc_ctl_debug_flags(struct xe_guc *guc)
>   
>   static u32 guc_ctl_feature_flags(struct xe_guc *guc)
>   {
> -	u32 flags = 0;
> +	u32 flags = GUC_CTL_ENABLE_LITE_RESTORE;
>   
>   	if (!guc_to_xe(guc)->info.skip_guc_pc)
>   		flags |= GUC_CTL_ENABLE_SLPC;
> diff --git a/drivers/gpu/drm/xe/xe_guc_fwif.h b/drivers/gpu/drm/xe/xe_guc_fwif.h
> index 01e3ab590c3a..08ffe59f22fa 100644
> --- a/drivers/gpu/drm/xe/xe_guc_fwif.h
> +++ b/drivers/gpu/drm/xe/xe_guc_fwif.h
> @@ -105,6 +105,7 @@ struct guc_update_exec_queue_policy {
>   
>   #define GUC_CTL_FEATURE			2
>   #define   GUC_CTL_ENABLE_SLPC		BIT(2)
> +#define   GUC_CTL_ENABLE_LITE_RESTORE	BIT(4)
>   #define   GUC_CTL_DISABLE_SCHEDULER	BIT(14)
>   
>   #define GUC_CTL_DEBUG			3


  reply	other threads:[~2024-10-10 17:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 17:31 [PATCH 0/1] drm/xe: enable lite restore fei.yang
2024-10-10 17:31 ` [PATCH 1/1] " fei.yang
2024-10-10 17:32   ` John Harrison [this message]
2024-10-11 13:47   ` Lucas De Marchi
2024-10-16 18:50     ` Yang, Fei
2024-10-10 17:32 ` ✓ CI.Patch_applied: success for drm/xe: enable lite restore (rev2) Patchwork
2024-10-10 17:32 ` ✓ CI.checkpatch: " Patchwork
2024-10-10 17:34 ` ✓ CI.KUnit: " Patchwork
2024-10-10 17:45 ` ✓ CI.Build: " Patchwork
2024-10-10 17:47 ` ✓ CI.Hooks: " Patchwork
2024-10-10 17:49 ` ✓ CI.checksparse: " Patchwork
2024-10-10 18:13 ` ✓ CI.BAT: " Patchwork
2024-10-11  2:47 ` ✗ CI.FULL: failure " Patchwork
2024-10-11 22:33 ` ✓ CI.Patch_applied: success for drm/xe: enable lite restore (rev3) Patchwork
2024-10-11 22:33 ` ✓ CI.checkpatch: " Patchwork
2024-10-11 22:34 ` ✓ CI.KUnit: " Patchwork
2024-10-11 22:46 ` ✓ CI.Build: " Patchwork
2024-10-11 22:48 ` ✓ CI.Hooks: " Patchwork
2024-10-11 22:50 ` ✓ CI.checksparse: " Patchwork
2024-10-11 23:18 ` ✓ CI.BAT: " Patchwork
2024-10-12  6:06 ` ✗ CI.FULL: failure " Patchwork
2024-10-15 19:28 ` ✓ CI.Patch_applied: success for drm/xe: enable lite restore (rev4) Patchwork
2024-10-15 19:28 ` ✓ CI.checkpatch: " Patchwork
2024-10-15 19:29 ` ✓ CI.KUnit: " Patchwork
2024-10-15 19:41 ` ✓ CI.Build: " Patchwork
2024-10-15 19:43 ` ✓ CI.Hooks: " Patchwork
2024-10-15 19:45 ` ✓ CI.checksparse: " Patchwork
2024-10-15 20:14 ` ✓ CI.BAT: " Patchwork
2024-10-16  6:51 ` ✗ CI.FULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17 16:27 [PATCH 0/1] drm/xe: enable lite restore fei.yang
2024-10-17 16:27 ` [PATCH 1/1] " fei.yang
2024-10-16 22:37 [PATCH 0/1] " fei.yang
2024-10-16 22:37 ` [PATCH 1/1] " fei.yang
2024-10-16 18:57 [PATCH 0/1] " fei.yang
2024-10-16 18:57 ` [PATCH 1/1] " fei.yang
2024-10-16 19:13   ` Souza, Jose
2024-10-16 22:39     ` Yang, Fei
2024-10-08 23:30 [PATCH 0/1] " fei.yang
2024-10-08 23:30 ` [PATCH 1/1] " fei.yang
2024-10-09 20:12   ` John Harrison

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=fb530ce7-17de-4600-a045-c2b91a66c5ae@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=fei.yang@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@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