From: Matthew Auld <matthew.auld@intel.com>
To: Jia Yao <jia.yao@intel.com>, intel-xe@lists.freedesktop.org
Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>, stable@vger.kernel.org
Subject: Re: [PATCH v8 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO
Date: Thu, 6 Aug 2026 12:11:40 +0100 [thread overview]
Message-ID: <424d6e9f-3e33-4f06-bbb3-11ce2d6e2607@intel.com> (raw)
In-Reply-To: <88b53afb-d7c1-4da1-9708-d0843be27b6d@intel.com>
On 05/08/2026 11:30, Matthew Auld wrote:
> On 04/08/2026 17:50, Jia Yao wrote:
>> Move the UM queues into a dedicated UC BO (ads->um_queue_bo) and avoid
>> CPU memset operations on it, which eliminates the CPU as a potential
>> cacheline-polluting agent and helps maintain consistency between GAM
>> writes and GuC reads.
Now pushed. I tweaked the commit message here, since we missed detailing
the contig related fixes.
>>
>> Fixes: 9c57bc08652a ("drm/xe/lnl: Drop force_probe requirement")
>> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>> Cc: Matthew Auld <matthew.auld@intel.com>
>> Cc: <stable@vger.kernel.org> # v6.12+
>> Signed-off-by: Jia Yao <jia.yao@intel.com>
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
next prev parent reply other threads:[~2026-08-06 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 16:50 [PATCH v8 0/3] drm/xe/guc_ads: allocate UM queues in a separate UC BO Jia Yao
2026-08-04 16:50 ` [PATCH v8 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Jia Yao
2026-08-05 10:30 ` Matthew Auld
2026-08-06 11:11 ` Matthew Auld [this message]
2026-08-04 16:50 ` [PATCH v8 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-04 16:50 ` [PATCH v8 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-04 16:58 ` ✓ CI.KUnit: success for drm/xe/guc_ads: allocate UM queues in a separate UC BO (rev6) Patchwork
2026-08-04 17:37 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-05 3:15 ` ✓ Xe.CI.FULL: " 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=424d6e9f-3e33-4f06-bbb3-11ce2d6e2607@intel.com \
--to=matthew.auld@intel.com \
--cc=gwan-gyeong.mun@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jia.yao@intel.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox