From: Matthew Brost <matthew.brost@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/xe/doc: Remove KEEP_ACTIVE feature
Date: Mon, 5 Jan 2026 17:54:59 -0800 [thread overview]
Message-ID: <aVxrc1dM5JZvXIPb@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20260106012920.2850975-6-niranjana.vishwanathapura@intel.com>
On Mon, Jan 05, 2026 at 05:29:16PM -0800, Niranjana Vishwanathapura wrote:
> The KEEP_ACTIVE feature is being reverted, update documentation.
>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_exec_queue.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
> index 529a40ca4002..b5737563ee14 100644
> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
> @@ -84,9 +84,8 @@
> * group is destroyed. The secondary queues hold a reference to the primary
> * queue thus preventing the group from being destroyed when user destroys
> * the primary queue. Once the primary queue is destroyed, secondary queues
> - * can't be added to the queue group, but they can continue to submit the
> - * jobs if the DRM_XE_MULTI_GROUP_KEEP_ACTIVE flag is set during the multi
> - * queue group creation.
> + * can't be added to the queue group and new job submissions on existing
> + * secondary queues are not allowed.
> *
> * The queues of a multi queue group can set their priority within the group
> * through the DRM_XE_EXEC_QUEUE_SET_PROPERTY_MULTI_QUEUE_PRIORITY property.
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-01-06 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 1:29 [PATCH 0/2] drm/xe: Remove multi-queue KEEP_ACTIVE feature Niranjana Vishwanathapura
2026-01-06 1:29 ` [PATCH 1/2] Revert "drm/xe/multi_queue: Support active group after primary is destroyed" Niranjana Vishwanathapura
2026-01-06 1:54 ` Matthew Brost
2026-01-06 1:29 ` [PATCH 2/2] drm/xe/doc: Remove KEEP_ACTIVE feature Niranjana Vishwanathapura
2026-01-06 1:54 ` Matthew Brost [this message]
2026-01-06 1:36 ` ✓ CI.KUnit: success for drm/xe: Remove multi-queue " Patchwork
2026-01-06 3:05 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-06 14:47 ` ✓ CI.KUnit: success for drm/xe: Remove multi-queue KEEP_ACTIVE feature (rev2) Patchwork
2026-01-06 15:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-06 16:58 ` ✓ Xe.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-01-06 19:10 [PATCH 0/2] drm/xe: Remove multi-queue KEEP_ACTIVE feature Niranjana Vishwanathapura
2026-01-06 19:10 ` [PATCH 2/2] drm/xe/doc: Remove " 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=aVxrc1dM5JZvXIPb@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@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