Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>
To: fei.yang@intel.com, intel-xe@lists.freedesktop.org
Cc: matthew.d.roper@intel.com
Subject: Re: [PATCH 0/1] drm/xe: enable lite restore
Date: Thu, 24 Oct 2024 10:48:26 -0700	[thread overview]
Message-ID: <c717c281-ec3e-4c40-be0d-71d668d5b51a@linux.intel.com> (raw)
In-Reply-To: <20241017162710.942553-1-fei.yang@intel.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

On 2024-10-17 12:27, fei.yang@intel.com wrote:
> From: Fei Yang<fei.yang@intel.com>
>
> The lite restore is a performance improvement feature which avoids
> unnecessary context switch (flush, save and rstore) if the incoming
> context has a ContextID matching that of the outgoing context. The
> scheduling is done by the Guc firmware, so on the driver side it's
> just a matter of setting corresponding GuC_CTL_FEATURE flag.
> This is supposed to be enabled by default, thus the flag is set
> unconditionally.
>
> Signed-off-by: Fei Yang<fei.yang@intel.com>

Please ensure that the version number is included when submitting revisions.

Kwan

> Fei Yang (1):
>    drm/xe: enable lite restore
>
>   drivers/gpu/drm/xe/xe_guc.c      | 2 +-
>   drivers/gpu/drm/xe/xe_guc_fwif.h | 1 +
>   2 files changed, 2 insertions(+), 1 deletion(-)
>

[-- Attachment #2: Type: text/html, Size: 1633 bytes --]

  parent reply	other threads:[~2024-10-24 17:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-17 16:42 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-17 16:42 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 16:43 ` ✓ CI.KUnit: " Patchwork
2024-10-17 16:55 ` ✓ CI.Build: " Patchwork
2024-10-17 16:57 ` ✓ CI.Hooks: " Patchwork
2024-10-17 16:59 ` ✓ CI.checksparse: " Patchwork
2024-10-17 17:25 ` ✗ CI.BAT: failure " Patchwork
2024-10-18  8:12 ` ✗ CI.FULL: " Patchwork
2024-10-18 17:28 ` ✓ CI.Patch_applied: success for drm/xe: enable lite restore (rev2) Patchwork
2024-10-18 17:28 ` ✓ CI.checkpatch: " Patchwork
2024-10-18 17:29 ` ✓ CI.KUnit: " Patchwork
2024-10-18 17:41 ` ✓ CI.Build: " Patchwork
2024-10-18 17:43 ` ✓ CI.Hooks: " Patchwork
2024-10-18 17:45 ` ✓ CI.checksparse: " Patchwork
2024-10-18 18:03 ` ✓ CI.BAT: " Patchwork
2024-10-19  9:38 ` ✗ CI.FULL: failure " Patchwork
2024-10-20  7:30 ` ✓ CI.Patch_applied: success for drm/xe: enable lite restore (rev3) Patchwork
2024-10-20  7:30 ` ✓ CI.checkpatch: " Patchwork
2024-10-20  7:31 ` ✓ CI.KUnit: " Patchwork
2024-10-20  7:43 ` ✓ CI.Build: " Patchwork
2024-10-20  7:45 ` ✓ CI.Hooks: " Patchwork
2024-10-20  7:47 ` ✓ CI.checksparse: " Patchwork
2024-10-20  8:12 ` ✓ CI.BAT: " Patchwork
2024-10-20  9:11 ` ✗ CI.FULL: failure " Patchwork
2024-10-24 17:48 ` Ngai-Mint Kwan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-16 22:37 [PATCH 0/1] drm/xe: enable lite restore fei.yang
2024-10-16 18:57 fei.yang
2024-10-10 17:31 fei.yang
2024-10-08 23:30 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=c717c281-ec3e-4c40-be0d-71d668d5b51a@linux.intel.com \
    --to=ngai-mint.kwan@linux.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