From: Matthew Auld <matthew.auld@intel.com>
To: "Mrozek, Michal" <michal.mrozek@intel.com>,
"Zhang, Carl" <carl.zhang@intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>
Cc: "Lucas De Marchi" <lucas.demarchi@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Souza, Jose" <jose.souza@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] drm/xe/uapi: disallow bind queue sharing
Date: Mon, 19 Jan 2026 15:09:26 +0000 [thread overview]
Message-ID: <8932c16e-ab31-493f-bc1a-c540f0ae5d6f@intel.com> (raw)
In-Reply-To: <DS7PR11MB6271DDAE76295D9280AB5CD7E788A@DS7PR11MB6271.namprd11.prod.outlook.com>
On 19/01/2026 14:14, Mrozek, Michal wrote:
>>> Michal, ping on this from compute POV?
>
> Compute is not using bind queues.
> PR is ok from compute perspective, even if we started to use those queues we would create a single queue per VM.
>
> Acked-by: Michal Mrozek <michal.mrozek@intel.com>
Thanks.
next prev parent reply other threads:[~2026-01-19 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 13:27 [PATCH v3 0/2] Some bind queue fixes Matthew Auld
2025-11-20 13:27 ` [PATCH v3 1/2] drm/xe/uapi: disallow bind queue sharing Matthew Auld
2025-11-20 15:06 ` Matthew Brost
2025-11-20 15:47 ` Yadav, Arvind
2025-11-20 15:34 ` Lucas De Marchi
2025-11-24 13:41 ` Matthew Auld
2025-12-18 20:40 ` Matthew Brost
2025-12-19 6:36 ` Zhang, Carl
2026-01-19 12:37 ` Matthew Auld
2026-01-19 14:14 ` Mrozek, Michal
2026-01-19 15:09 ` Matthew Auld [this message]
2025-11-20 13:27 ` [PATCH v3 2/2] drm/xe/migrate: fix job lock assert Matthew Auld
2025-11-20 15:30 ` Yadav, Arvind
2025-11-20 13:52 ` ✗ CI.checkpatch: warning for Some bind queue fixes (rev3) Patchwork
2025-11-20 13:53 ` ✓ CI.KUnit: success " Patchwork
2025-11-20 14:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-20 17:38 ` ✗ Xe.CI.Full: failure " 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=8932c16e-ab31-493f-bc1a-c540f0ae5d6f@intel.com \
--to=matthew.auld@intel.com \
--cc=carl.zhang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.mrozek@intel.com \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.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