From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [CI] drm/xe: Don't make exec_queues persistent by default
Date: Thu, 25 Jan 2024 11:59:33 +0100 [thread overview]
Message-ID: <20240125105933.5159-1-thomas.hellstrom@linux.intel.com> (raw)
A first step in avoiding persistent exec_queue handling.
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.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 c0b7434e78f1..bee07bc29f89 100644
--- a/drivers/gpu/drm/xe/xe_exec_queue.c
+++ b/drivers/gpu/drm/xe/xe_exec_queue.c
@@ -707,7 +707,7 @@ int xe_exec_queue_create_ioctl(struct drm_device *dev, void *data,
/* The migration vm doesn't hold rpm ref */
xe_device_mem_access_get(xe);
- flags = EXEC_QUEUE_FLAG_PERSISTENT | EXEC_QUEUE_FLAG_VM |
+ flags = EXEC_QUEUE_FLAG_VM |
(id ? EXEC_QUEUE_FLAG_BIND_ENGINE_CHILD : 0);
migrate_vm = xe_migrate_get_vm(gt_to_tile(gt)->migrate);
@@ -760,8 +760,7 @@ int xe_exec_queue_create_ioctl(struct drm_device *dev, void *data,
q = xe_exec_queue_create(xe, vm, logical_mask,
args->width, hwe,
- xe_vm_in_lr_mode(vm) ? 0 :
- EXEC_QUEUE_FLAG_PERSISTENT,
+ 0,
args->extensions);
up_read(&vm->lock);
xe_vm_put(vm);
--
2.43.0
next reply other threads:[~2024-01-25 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 10:59 Thomas Hellström [this message]
2024-01-25 11:08 ` ✓ CI.Patch_applied: success for drm/xe: Don't make exec_queues persistent by default Patchwork
2024-01-25 11:09 ` ✓ CI.checkpatch: " Patchwork
2024-01-25 11:09 ` ✓ CI.KUnit: " Patchwork
2024-01-25 11:17 ` ✓ CI.Build: " Patchwork
2024-01-25 11:17 ` ✓ CI.Hooks: " Patchwork
2024-01-25 11:18 ` ✓ CI.checksparse: " Patchwork
2024-01-25 11:42 ` ✓ CI.BAT: " 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=20240125105933.5159-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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.