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: Wed, 9 Oct 2024 13:12:53 -0700 [thread overview]
Message-ID: <61465e66-ff3f-49af-aa1a-0c899e90d486@intel.com> (raw)
In-Reply-To: <20241008233059.125021-2-fei.yang@intel.com>
On 10/8/2024 16:30, 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>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 2 ++
> drivers/gpu/drm/xe/xe_guc_fwif.h | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 8570b1218287..e1dad02b0770 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -75,6 +75,8 @@ static u32 guc_ctl_feature_flags(struct xe_guc *guc)
> if (!guc_to_xe(guc)->info.skip_guc_pc)
> flags |= GUC_CTL_ENABLE_SLPC;
>
> + flags |= GUC_CTL_ENABLE_LITE_RESTORE;
> +
Given that this is unconditional, you could put this before the
conditional one and make it a straight assignment (and drop the =0 from
the declaration line).
john.
> return flags;
> }
>
> 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
next prev parent reply other threads:[~2024-10-09 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 23:30 [PATCH 0/1] drm/xe: enable lite restore fei.yang
2024-10-08 23:30 ` [PATCH 1/1] " fei.yang
2024-10-09 20:12 ` John Harrison [this message]
2024-10-08 23:32 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-08 23:32 ` ✓ CI.checkpatch: " Patchwork
2024-10-08 23:33 ` ✓ CI.KUnit: " Patchwork
2024-10-08 23:45 ` ✓ CI.Build: " Patchwork
2024-10-08 23:47 ` ✓ CI.Hooks: " Patchwork
2024-10-08 23:48 ` ✓ CI.checksparse: " Patchwork
2024-10-09 0:06 ` ✓ CI.BAT: " Patchwork
2024-10-09 9:05 ` ✗ CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-10 17:31 [PATCH 0/1] " fei.yang
2024-10-10 17:31 ` [PATCH 1/1] " fei.yang
2024-10-10 17:32 ` John Harrison
2024-10-11 13:47 ` Lucas De Marchi
2024-10-16 18:50 ` Yang, Fei
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-16 22:37 [PATCH 0/1] " fei.yang
2024-10-16 22:37 ` [PATCH 1/1] " fei.yang
2024-10-17 16:27 [PATCH 0/1] " fei.yang
2024-10-17 16:27 ` [PATCH 1/1] " fei.yang
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=61465e66-ff3f-49af-aa1a-0c899e90d486@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 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.