From: Matthew Auld <matthew.auld@intel.com>
To: Jan Maslak <jan.maslak@intel.com>, intel-xe@lists.freedesktop.org
Cc: matthew.brost@intel.com, thomas.hellstrom@linux.intel.com,
rodrigo.vivi@intel.com,
Christoph Manszewski <christoph.manszewski@intel.com>
Subject: Re: [PATCH v2 4/4] drm/xe/tests: Add xe_migrate_access_memory subtest
Date: Fri, 4 Sep 2026 13:14:49 +0100 [thread overview]
Message-ID: <49ec8460-4099-4ca6-962e-cf819d8737fa@intel.com> (raw)
In-Reply-To: <20260622103449.3335928-5-jan.maslak@intel.com>
On 22/06/2026 11:34, Jan Maslak wrote:
> From: Christoph Manszewski <christoph.manszewski@intel.com>
>
> Add a new xe_migrate subtest for vram to sram migration works:
> - when the dst address is not 4-byte aligned
> - when the dst address in not 4-byte aligned but the migration size is
> - when src BO offset is not 4-byte aligned
>
> Signed-off-by: Christoph Manszewski <christoph.manszewski@intel.com>
> Signed-off-by: Jan Maslak <jan.maslak@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2026-09-04 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 10:34 [PATCH v2 0/4] drm/xe/xe_migrate: Fix memory corruption with unaligned dst in MEM_COPY Jan Maslak
2026-06-22 10:34 ` [PATCH v2 1/4] drm/xe/xe_migrate: Align MEM_COPY pitch with destination address Jan Maslak
2026-08-17 16:39 ` Matthew Auld
2026-08-31 19:10 ` Jan Maslak
2026-09-07 13:59 ` Matthew Auld
2026-06-22 10:34 ` [PATCH v2 2/4] drm/xe/xe_migrate: Fix page tracking in access_memory Jan Maslak
2026-09-07 16:19 ` Matthew Auld
2026-06-22 10:34 ` [PATCH v2 3/4] drm/xe/xe_migrate: Optimize unaligned access_memory copies Jan Maslak
2026-09-08 10:39 ` Matthew Auld
2026-06-22 10:34 ` [PATCH v2 4/4] drm/xe/tests: Add xe_migrate_access_memory subtest Jan Maslak
2026-09-04 12:14 ` Matthew Auld [this message]
2026-06-22 15:58 ` ✗ CI.checkpatch: warning for drm/xe/xe_migrate: Fix memory corruption with unaligned dst in MEM_COPY (rev2) Patchwork
2026-06-22 15:59 ` ✓ CI.KUnit: success " Patchwork
2026-06-22 16:55 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-22 19:27 ` ✗ Xe.CI.FULL: " 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=49ec8460-4099-4ca6-962e-cf819d8737fa@intel.com \
--to=matthew.auld@intel.com \
--cc=christoph.manszewski@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jan.maslak@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.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.