From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v3 0/3] Some eviction fixes
Date: Mon, 30 Oct 2023 16:10:17 +0000 [thread overview]
Message-ID: <20231030161016.54300-5-matthew.auld@intel.com> (raw)
Fixes the scary corruption issues seen around evicting VRAM, as picked up by the
IGTs written by Zbigniew [1].
v2: Some improvements suggested by Matt B.
v3: Use ctx->interruptible for the wait (Thomas).
[1] https://patchwork.freedesktop.org/series/124626/
--
2.41.0
next reply other threads:[~2023-10-30 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:10 Matthew Auld [this message]
2023-10-30 16:10 ` [Intel-xe] [PATCH v3 1/3] drm/xe/migrate: fix MI_ARB_ON_OFF usage Matthew Auld
2023-10-30 16:10 ` [Intel-xe] [PATCH v3 2/3] drm/xe/bo: consider dma-resv fences for clear job Matthew Auld
2023-10-30 16:10 ` [Intel-xe] [PATCH v3 3/3] drm/xe/bo: sync kernel fences for KMD buffers Matthew Auld
2023-10-30 16:13 ` Thomas Hellström
2023-10-30 17:06 ` [Intel-xe] ✓ CI.Patch_applied: success for Some eviction fixes (rev3) Patchwork
2023-10-30 17:06 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-30 17:07 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-30 17:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-30 17:15 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-30 17:16 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-10-30 17:45 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-10-31 8:17 ` [Intel-xe] ✓ CI.Patch_applied: success for Some eviction fixes (rev4) Patchwork
2023-10-31 8:17 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-31 8:19 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-31 8:26 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-31 8:26 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-31 8:27 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-10-31 9:09 ` [Intel-xe] ✓ CI.BAT: " 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=20231030161016.54300-5-matthew.auld@intel.com \
--to=matthew.auld@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.