Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <lucas.demarchi@intel.com>
Subject: Re: [PATCH v3 2/2] drm/xe: Clear GGTT in xe_bo_restore_kernel
Date: Wed, 13 Nov 2024 06:43:12 -0800	[thread overview]
Message-ID: <ZzS7AJd24jmRq+sB@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <3c2203a0-2731-4f5b-bf58-ecec21662002@intel.com>

On Wed, Nov 13, 2024 at 12:55:35PM +0000, Matthew Auld wrote:
> On 06/11/2024 18:35, Matthew Brost wrote:
> > Part of what xe_bo_restore_kernel does, is restore BO's GGTT mappings
> > which may have been lost during a power state change. Missing is
> > restoring the GGTT entries without BO mappings to a known state (e.g.,
> > scratch pages). Update xe_bo_restore_kernel to clear the entire GGTT
> > before restoring BO's GGTT mappings.
> > 
> > v2:
> >   - Include missing local change of tile and id variable (CI)
> > v3:
> >   - Fixed kernel doc (CI)
> > 
> > Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
> > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > Cc: <stable@vger.kernel.org> # v6.8+
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>

Thanks for the review but I'm pretty sure this is breaking display... See
our CI runs, hard to exactly tell because of the instability there. I'm
thinking only the parts GGTT without nodes need to be cleared, i.e., do
what xe_ggtt_initial_clear does.

I am a little unsure how the display code restores it GGTT mappings
though as it appears that code bypasses BOs? Do you have any idea?

Matt

  reply	other threads:[~2024-11-13 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 18:35 [PATCH v3 1/2] drm/xe: improve hibernation on igpu Matthew Brost
2024-11-06 18:35 ` [PATCH v3 2/2] drm/xe: Clear GGTT in xe_bo_restore_kernel Matthew Brost
2024-11-13 12:55   ` Matthew Auld
2024-11-13 14:43     ` Matthew Brost [this message]
2024-11-13 16:44       ` Matthew Auld
2024-11-06 18:39 ` ✓ CI.Patch_applied: success for series starting with [v3,1/2] drm/xe: improve hibernation on igpu Patchwork
2024-11-06 18:39 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-06 18:41 ` ✓ CI.KUnit: success " Patchwork
2024-11-06 18:52 ` ✓ CI.Build: " Patchwork
2024-11-06 18:54 ` ✓ CI.Hooks: " Patchwork
2024-11-06 18:56 ` ✓ CI.checksparse: " Patchwork
2024-11-08  1:11 ` ✗ CI.FULL: failure " Patchwork
2024-11-08  4:37 ` ✓ CI.Patch_applied: success for series starting with [v3,1/2] drm/xe: improve hibernation on igpu (rev2) Patchwork
2024-11-08  4:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-08  4:38 ` ✓ CI.KUnit: success " Patchwork
2024-11-08  4:50 ` ✓ CI.Build: " Patchwork
2024-11-08  4:52 ` ✓ CI.Hooks: " Patchwork
2024-11-08  4:54 ` ✓ CI.checksparse: " Patchwork
2024-11-09 10:34 ` ✗ CI.FULL: failure " 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=ZzS7AJd24jmRq+sB@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@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