All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jia Yao <jia.yao@intel.com>
Cc: stable@vger.kernel.org,
	"Gwan-gyeong Mun" <gwan-gyeong.mun@intel.com>,
	"Matthew Auld" <matthew.auld@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO
Date: Mon, 24 Aug 2026 19:02:58 +0200	[thread overview]
Message-ID: <2026082417-detonate-glacial-6417@gregkh> (raw)
In-Reply-To: <20260824165208.498797-1-jia.yao@intel.com>

On Mon, Aug 24, 2026 at 04:52:06PM +0000, Jia Yao wrote:
> Move the UM queues into a dedicated 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.
> 
> We also need to ensure the base_dpa for the queue is contiguous on hw
> where this is used instead of a GGTT address. Another good reason to
> split this out to a separate BO.
> 
> 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>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Link: https://patch.msgid.link/20260804165057.129529-2-jia.yao@intel.com
> (cherry picked from commit 6af05de0dc19bbf3aaeec2020fe48b37c834b811)
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> (cherry picked from commit 99b01815957bd7d848420cb697f79ed11f7f215c)
> ---
>  drivers/gpu/drm/xe/xe_bo.h            | 14 +++++
>  drivers/gpu/drm/xe/xe_guc.c           |  6 ++
>  drivers/gpu/drm/xe/xe_guc_ads.c       | 90 +++++++++++++++++----------
>  drivers/gpu/drm/xe/xe_guc_ads_types.h |  5 ++
>  4 files changed, 83 insertions(+), 32 deletions(-)

What stable tree(s) are these patches for?

And what's with the crazy 2 cherry picked lines?  You all know better
than to attempt to mess this up even more...

  parent reply	other threads:[~2026-08-24 17:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 11:13 FAILED: patch "[PATCH] drm/xe/guc_ads: allocate UM queues in a separate BO" failed to apply to 6.18-stable tree gregkh
2026-08-20 16:08 ` [PATCH 6.18.y] drm/xe/guc_ads: allocate UM queues in a separate BO Jia Yao
2026-08-24 16:52 ` [PATCH 1/3] " Jia Yao
2026-08-24 16:52   ` [PATCH 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-24 16:52   ` [PATCH 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-24 17:02   ` Greg KH [this message]
2026-08-24 17:12     ` [PATCH 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Yao, Jia
2026-08-25  3:45       ` Yao, Jia
2026-08-25  3:42 ` [PATCH 6.18.y " Jia Yao
2026-08-25  3:42   ` [PATCH 6.18.y 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-25  8:27     ` Greg KH
2026-08-25  3:42   ` [PATCH 6.18.y 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-25  8:28     ` Greg KH
2026-08-25 23:27       ` Yao, Jia
2026-08-25  8:27   ` [PATCH 6.18.y 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Greg KH
2026-08-25 23:30 ` Jia Yao
2026-08-25 23:30   ` [PATCH 6.18.y 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-25 23:30   ` [PATCH 6.18.y 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-27  5:17   ` [PATCH 6.18.y 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2026-08-20 11:13 FAILED: patch "[PATCH] drm/xe/guc_ads: use uncached mapping for UM queue BO" failed to apply to 6.12-stable tree gregkh
2026-08-24 16:48 ` [PATCH 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Jia Yao

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=2026082417-detonate-glacial-6417@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=jia.yao@intel.com \
    --cc=matthew.auld@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 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.