From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Francois Dugast <francois.dugast@intel.com>,
David Airlie <airlied@gmail.com>,
intel-xe@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [RFC PATCH] drm/xe/uapi: Remove support for persistent exec_queues
Date: Wed, 31 Jan 2024 16:56:37 -0500 [thread overview]
Message-ID: <ZbrCFRpGA3WmZNit@intel.com> (raw)
In-Reply-To: <m3dktl4dhsaz6doivscmbmlohgwpwrsp2r4h77jysm23ltptla@zvxbcxzhvyob>
On Tue, Jan 30, 2024 at 08:24:07AM -0600, Lucas De Marchi wrote:
> On Tue, Jan 30, 2024 at 01:52:20PM +0100, Thomas Hellström wrote:
> > Persistent exec_queues delays explicit destruction of exec_queues
> > until they are done executing, but destruction on process exit
> > is still immediate. It turns out no UMD is relying on this
> > functionality, so remove it. If there turns out to be a use-case
> > in the future, let's re-add.
> >
> > Persistent exec_queues were never used for LR VMs
> >
> > Open: Should we renumber the exec_queue properties, or leave a hole
> > as in this patch.
>
> I think it's fine to leave a hole
>
> > diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> > index 50bbea0992d9..4124284e4cce 100644
> > --- a/include/uapi/drm/xe_drm.h
> > +++ b/include/uapi/drm/xe_drm.h
> > @@ -1045,7 +1045,7 @@ struct drm_xe_exec_queue_create {
> > #define DRM_XE_EXEC_QUEUE_SET_PROPERTY_PRIORITY 0
> > #define DRM_XE_EXEC_QUEUE_SET_PROPERTY_TIMESLICE 1
> > #define DRM_XE_EXEC_QUEUE_SET_PROPERTY_PREEMPTION_TIMEOUT 2
> > -#define DRM_XE_EXEC_QUEUE_SET_PROPERTY_PERSISTENCE 3
> > +#define DRM_XE_EXEC_QUEUE_SET_UNUSED_1 3
>
> but I don't think we should add this define here. We could eventually
> just use this whole.
Leave the hole and the define and then add checks to refuse the ioctl
if this property number is selected.
>
>
>
> Lucas De Marchi
next prev parent reply other threads:[~2024-01-31 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 12:52 [RFC PATCH] drm/xe/uapi: Remove support for persistent exec_queues Thomas Hellström
2024-01-30 12:55 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-30 12:55 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-30 12:56 ` ✓ CI.KUnit: success " Patchwork
2024-01-30 13:03 ` ✓ CI.Build: " Patchwork
2024-01-30 13:04 ` ✓ CI.Hooks: " Patchwork
2024-01-30 13:05 ` ✓ CI.checksparse: " Patchwork
2024-01-30 13:26 ` ✓ CI.BAT: " Patchwork
2024-01-30 14:24 ` [RFC PATCH] " Lucas De Marchi
2024-01-31 21:56 ` Rodrigo Vivi [this message]
2024-01-31 19:41 ` Dave Airlie
2024-01-31 21:55 ` Rodrigo Vivi
2024-02-01 17:00 ` Niranjana Vishwanathapura
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=ZbrCFRpGA3WmZNit@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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.