From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com
Subject: Re: [PATCH v3 5/6] drm/xe: Set XE_BO_FLAG_PINNED in migrate selftest BOs
Date: Mon, 21 Oct 2024 10:50:13 +0100 [thread overview]
Message-ID: <74cbcdff-af60-4a3c-a76a-80edfed9b81b@intel.com> (raw)
In-Reply-To: <20241019192030.1505020-6-matthew.brost@intel.com>
On 19/10/2024 20:20, Matthew Brost wrote:
> We only allow continguous BOs to be vmapped, set XE_BO_FLAG_PINNED on
> BOs in migrate selftest as this forces continguous BOs and selftest uses
> vmaps.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2024-10-21 9:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 19:20 [PATCH v3 0/6] Fix non-contiguous VRAM BO access in Xe Matthew Brost
2024-10-19 19:20 ` [PATCH v3 1/6] drm/ttm: Add ttm_bo_access Matthew Brost
2024-10-19 19:20 ` [PATCH v3 2/6] drm/xe: Add xe_ttm_access_memory Matthew Brost
2024-10-19 19:20 ` [PATCH v3 3/6] drm/xe: Update xe_ttm_access_memory to use GPU for non-visible access Matthew Brost
2024-10-21 10:15 ` Matthew Auld
2024-10-21 11:01 ` Thomas Hellström
2024-10-21 17:18 ` Matthew Brost
2024-10-21 17:02 ` Matthew Brost
2024-10-19 19:20 ` [PATCH v3 4/6] drm/xe: Use ttm_bo_access in xe_vm_snapshot_capture_delayed Matthew Brost
2024-10-21 9:07 ` Matthew Auld
2024-10-21 16:58 ` Matthew Brost
2024-10-19 19:20 ` [PATCH v3 5/6] drm/xe: Set XE_BO_FLAG_PINNED in migrate selftest BOs Matthew Brost
2024-10-21 9:50 ` Matthew Auld [this message]
2024-10-19 19:20 ` [PATCH v3 6/6] drm/xe: Only allow contiguous BOs to use xe_bo_vmap Matthew Brost
2024-10-21 9:32 ` Matthew Auld
2024-10-19 19:25 ` ✓ CI.Patch_applied: success for Fix non-contiguous VRAM BO access in Xe (rev3) Patchwork
2024-10-19 19:25 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-19 19:27 ` ✓ CI.KUnit: success " Patchwork
2024-10-19 19:38 ` ✓ CI.Build: " Patchwork
2024-10-19 19:40 ` ✓ CI.Hooks: " Patchwork
2024-10-19 19:42 ` ✗ CI.checksparse: warning " Patchwork
2024-10-19 20:07 ` ✓ CI.BAT: success " Patchwork
2024-10-19 21:06 ` ✗ 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=74cbcdff-af60-4a3c-a76a-80edfed9b81b@intel.com \
--to=matthew.auld@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox