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 6.18.y 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX
Date: Tue, 25 Aug 2026 10:27:44 +0200	[thread overview]
Message-ID: <2026082512-emergency-macaw-eaaf@gregkh> (raw)
In-Reply-To: <20260825034224.642641-2-jia.yao@intel.com>

On Tue, Aug 25, 2026 at 03:42:23AM +0000, Jia Yao wrote:
> On iGPU, the UM queue BO is allocated in system memory. On dGFX, the BO
> was previously created in system memory and later reallocated in
> xe_guc_realloc_post_hwconfig().  Allocate the UM queue BO directly in
> VRAM on dGFX, where it is ultimately required.
> 
> 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-3-jia.yao@intel.com
> (cherry picked from commit ace076ef0a854ab5940bacc539bf66afd61d118c)

Same here, this commit id is not in Linus's, or any stable kernel trees.
Where is it coming from?

thanks,

greg k-h

  reply	other threads:[~2026-08-25  8:27 UTC|newest]

Thread overview: 19+ 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   ` [PATCH 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Greg KH
2026-08-24 17:12     ` 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 [this message]
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

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=2026082512-emergency-macaw-eaaf@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.