Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 0/4] Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE
Date: Tue, 19 Sep 2023 09:14:06 -0400	[thread overview]
Message-ID: <ZQmenqsn4JVHeoDr@intel.com> (raw)
In-Reply-To: <20230915233445.2241554-1-matthew.brost@intel.com>

On Fri, Sep 15, 2023 at 04:34:41PM -0700, Matthew Brost wrote:
> Backwards backing uAPI changes, getting on the list.

Patch 2 breaks compatibility.

> 
> First 3 patches already on the list [1] and free to merge as soon as it
> gets an RB.

Please do not merge this today as I'm getting these patches with
the others that Francois and myself are collecting to have a one-time
shot on breaking the compatibility.

> 
> The required IGT changes are also on the list [2].
> 
> Matt
> 
> [1] https://patchwork.freedesktop.org/series/123820/
> [2] https://patchwork.freedesktop.org/series/123821/
> 
> Matthew Brost (4):
>   drm/xe: Fix xe_exec_queue_is_idle for parallel exec queues
>   drm/xe: Deprecate XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE
>     implementation
>   drm/xe: Rename exec_queue_kill_compute to
>     xe_vm_remove_compute_exec_queue
>   drm/xe: Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE from uAPI
> 
>  drivers/gpu/drm/xe/xe_exec_queue.c       | 97 +++++++-----------------
>  drivers/gpu/drm/xe/xe_exec_queue_types.h |  6 +-
>  drivers/gpu/drm/xe/xe_vm.c               | 21 +++++
>  drivers/gpu/drm/xe/xe_vm.h               |  1 +
>  include/uapi/drm/xe_drm.h                | 19 ++---
>  5 files changed, 57 insertions(+), 87 deletions(-)
> 
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2023-09-19 13:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 23:34 [Intel-xe] [PATCH v2 0/4] Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE Matthew Brost
2023-09-15 23:34 ` [Intel-xe] [PATCH v2 1/4] drm/xe: Fix xe_exec_queue_is_idle for parallel exec queues Matthew Brost
2023-09-18  4:54   ` Niranjana Vishwanathapura
2023-09-15 23:34 ` [Intel-xe] [PATCH v2 2/4] drm/xe: Deprecate XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE implementation Matthew Brost
2023-09-18  4:53   ` Niranjana Vishwanathapura
2023-09-15 23:34 ` [Intel-xe] [PATCH v2 3/4] drm/xe: Rename exec_queue_kill_compute to xe_vm_remove_compute_exec_queue Matthew Brost
2023-09-18  4:53   ` Niranjana Vishwanathapura
2023-09-18 15:34     ` Matthew Brost
2023-09-15 23:34 ` [Intel-xe] [PATCH v2 4/4] drm/xe: Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE from uAPI Matthew Brost
2023-09-16  3:10 ` [Intel-xe] ✓ CI.Patch_applied: success for Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE (rev2) Patchwork
2023-09-16  3:11 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-16  3:12 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-16  3:19 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-16  3:19 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-16  3:21 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-09-16  3:59 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-19 13:14 ` Rodrigo Vivi [this message]
2023-09-19 13:35   ` [Intel-xe] [PATCH v2 0/4] Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE Rodrigo Vivi
2023-09-19 14:57     ` Matthew Brost

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=ZQmenqsn4JVHeoDr@intel.com \
    --to=rodrigo.vivi@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