Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v6 4/7] drm/xe: Convert multiple bind ops into single job
Date: Thu, 27 Jun 2024 17:20:46 +0100	[thread overview]
Message-ID: <cf35f4ca-8e79-4cd1-ae92-ba70eff1d0e6@intel.com> (raw)
In-Reply-To: <20240626211546.4099339-5-matthew.brost@intel.com>

On 26/06/2024 22:15, Matthew Brost wrote:
> This aligns with the uAPI of an array of binds or single bind that
> results in multiple GPUVA ops to be considered a single atomic
> operations.
> 
> The bind-array-enobufs is roughly:
> - xe_vma_ops is a list of xe_vma_op (GPUVA op)
> - each xe_vma_op resolves to 0-3 PT ops
> - xe_vma_ops creates a single job
> - if at any point during binding a failure occurs, xe_vma_ops contains
>    the information necessary unwind the PT and VMA (GPUVA) state
> 
> v2:
>   - add missing dma-resv slot reservation (CI, testing)
> v4:
>   - Fix TLB invalidation (Paulo)
>   - Add missing xe_sched_job_last_fence_add/test_dep check (Inspection)
> v5:
>   - Invert i, j usage (Matthew Auld)
>   - Add helper to test and add job dep (Matthew Auld)
>   - Return on anything but -ETIME for cpu bind (Matthew Auld)
>   - Return -ENOBUFS if suballoc of BB fails due to size (Matthew Auld)
>   - s/do/Do (Matthew Auld)
>   - Add missing comma (Matthew Auld)
>   - Do not assign return value to xe_range_fence_insert (Matthew Auld)
> v6:
>   - s/0x1ff/MAX_PTE_PER_SDI (Matthew Auld, CI)
>   - Check to large of SA in Xe to avoid triggering WARN (Matthew Auld)
>   - Fix checkpatch issues
> 
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Auld <matthew.auld@intel.com>

  reply	other threads:[~2024-06-27 16:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 21:15 [PATCH v6 0/7] Convert multiple bind ops to 1 job Matthew Brost
2024-06-26 21:15 ` [PATCH v6 1/7] drm/xe: s/xe_tile_migrate_engine/xe_tile_migrate_exec_queue Matthew Brost
2024-06-26 21:15 ` [PATCH v6 2/7] drm/xe: Add xe_vm_pgtable_update_op to xe_vma_ops Matthew Brost
2024-06-26 21:15 ` [PATCH v6 3/7] drm/xe: Add xe_exec_queue_last_fence_test_dep Matthew Brost
2024-06-27 16:36   ` Matthew Auld
2024-06-27 17:59     ` Matthew Brost
2024-06-26 21:15 ` [PATCH v6 4/7] drm/xe: Convert multiple bind ops into single job Matthew Brost
2024-06-27 16:20   ` Matthew Auld [this message]
2024-06-26 21:15 ` [PATCH v6 5/7] drm/xe: Update VM trace events Matthew Brost
2024-06-26 21:15 ` [PATCH v6 6/7] drm/xe: Update PT layer with better error handling Matthew Brost
2024-06-28 15:00   ` Matthew Auld
2024-06-28 15:55     ` Matthew Brost
2024-06-26 21:15 ` [PATCH v6 7/7] drm/xe: Add VM bind IOCTL error injection Matthew Brost
2024-06-26 23:28 ` ✓ CI.Patch_applied: success for Convert multiple bind ops to 1 job (rev6) Patchwork
2024-06-26 23:29 ` ✓ CI.checkpatch: " Patchwork
2024-06-26 23:30 ` ✓ CI.KUnit: " Patchwork
2024-06-26 23:42 ` ✓ CI.Build: " Patchwork
2024-06-26 23:44 ` ✓ CI.Hooks: " Patchwork
2024-06-26 23:45 ` ✓ CI.checksparse: " Patchwork
2024-06-27  0:09 ` ✓ CI.BAT: " Patchwork
2024-06-27 12:29 ` ✓ 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=cf35f4ca-8e79-4cd1-ae92-ba70eff1d0e6@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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