All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>, "Jia Yao" <jia.yao@intel.com>,
	"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.12.y 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO
Date: Thu, 27 Aug 2026 01:17:58 -0400	[thread overview]
Message-ID: <20260827050834.10008.stable-daily@kernel.org> (raw)
In-Reply-To: <20260825034113.642528-1-jia.yao@intel.com>

> (cherry picked from commit 6af05de0dc19bbf3aaeec2020fe48b37c834b811)

This series needs a v2 before we can take it...

The cherry-pick lines name drm-xe-next commits that are not in Linus' tree.

The series also does not build on 6.12, and 2/3 is not safe there:

 - XE_BO_FLAG_PINNED_NORESTORE does not exist on 6.12; it arrives with
   045448da87bf ("drm/xe: Add XE_BO_FLAG_PINNED_NORESTORE") in v6.16.
 - xe_guc_using_main_gamctrl_queues() does not exist either. It comes from
   94edd6518613 ("drm/xe/xe3p_lpm: Configure MAIN_GAMCTRL_QUEUE_SELECT").
   You dropped it from guc_um_init_params(), but the second call site in
   xe_guc_ads_init() is still there.
 - On 6.12, xe_guc_ads_init() runs before xe_vram_probe(), so 2/3's
   XE_BO_FLAG_VRAM_IF_DGFX reaches add_vram() with no VRAM manager yet: a
   NULL deref at probe on Battlemage. 2/3 also removes the
   xe_managed_bo_reinit_in_vram() call, which is 6.12's only working VRAM
   path.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2026-08-27  5:18 UTC|newest]

Thread overview: 11+ 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.12-stable tree gregkh
2026-08-20 18:30 ` [PATCH 6.12.y] drm/xe/guc_ads: allocate UM queues in a separate BO Jia Yao
2026-08-25  3:41 ` [PATCH 6.12.y 1/3] " Jia Yao
2026-08-25  3:41   ` [PATCH 6.12.y 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-25  3:41   ` [PATCH 6.12.y 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-25  8:29   ` [PATCH 6.12.y 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Greg KH
2026-08-25 23:26     ` Yao, Jia
2026-08-25 23:47       ` Yao, Jia
2026-08-27  5:17   ` Sasha Levin [this message]
2026-08-27 15:04     ` Yao, Jia
2026-08-28  5:37       ` Yao, Jia

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=20260827050834.10008.stable-daily@kernel.org \
    --to=sashal@kernel.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.