From: Matthew Brost <matthew.brost@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@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 14:57:19 +0000 [thread overview]
Message-ID: <ZQm2z3PSaIm3ZPHB@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <ZQmjph//w3+9mKOI@intel.com>
On Tue, Sep 19, 2023 at 09:35:34AM -0400, Rodrigo Vivi wrote:
> On Tue, Sep 19, 2023 at 09:14:06AM -0400, Rodrigo Vivi wrote:
> > 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.
How? I just tested again with old IGTs and everything seems to work. Not
my intent to break the uAPI.
> >
> > >
> > > 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.
>
> I just noticed that my message came too late. Since it breaks uapi
> compatibility and no userspace, not even igt is ready yet, I have
> removed the patches and force pushed drm-xe-next.
>
> Please do not push these patches again since they will be part of
> the uapi series we are preparing and will be pushed when the UMDs
> are ready for that.
>
I see that these are reverted, fine with holding off on pushing these.
Matt
> Thanks,
> Rodrigo.
>
>
> >
> > >
> > > 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
> > >
prev parent reply other threads:[~2023-09-19 14:58 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 ` [Intel-xe] [PATCH v2 0/4] Remove XE_EXEC_QUEUE_SET_PROPERTY_COMPUTE_MODE Rodrigo Vivi
2023-09-19 13:35 ` Rodrigo Vivi
2023-09-19 14:57 ` Matthew Brost [this message]
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=ZQm2z3PSaIm3ZPHB@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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