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 v7 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX
Date: Tue, 4 Aug 2026 08:45:00 +0100 [thread overview]
Message-ID: <0a0db7a1-a3ad-45a3-9b59-723d539fbe88@intel.com> (raw)
In-Reply-To: <20260803200838.98826-3-jia.yao@intel.com>
On 03/08/2026 21:08, 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>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 6 ------
> drivers/gpu/drm/xe/xe_guc_ads.c | 17 ++++++++++-------
> 2 files changed, 10 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 4f132bf8539d..4286bd05c686 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -732,12 +732,6 @@ static int xe_guc_realloc_post_hwconfig(struct xe_guc *guc)
> if (ret)
> return ret;
>
> - if (guc->ads.um_queue_bo) {
> - ret = xe_managed_bo_reinit_in_vram(xe, tile, &guc->ads.um_queue_bo);
> - if (ret)
> - return ret;
> - }
> -
> return 0;
> }
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_ads.c b/drivers/gpu/drm/xe/xe_guc_ads.c
> index ef8e9cc35c8c..a69ec584cc0f 100644
> --- a/drivers/gpu/drm/xe/xe_guc_ads.c
> +++ b/drivers/gpu/drm/xe/xe_guc_ads.c
> @@ -446,19 +446,22 @@ int xe_guc_ads_init(struct xe_guc_ads *ads)
> /*
> * Allocate a separate BO for the HW fault ring (UM queues).
> *
> - * Round the size up to the next power of two so that
> + * Round the size up to the next power of two so that on iGPU
> * (system memory, no IOMMU) the TTM pool issues a single
> * alloc_pages(order=N) call, maximising the chance of getting
> * a physically contiguous block. GuC requires contiguous DPA.
> */
> - size_t um_size = roundup_pow_of_two(GUC_UM_QUEUE_SIZE *
> + size_t um_size = IS_DGFX(xe) ?
> + GUC_UM_QUEUE_SIZE * GUC_UM_HW_QUEUE_MAX :
> + roundup_pow_of_two(GUC_UM_QUEUE_SIZE *
> GUC_UM_HW_QUEUE_MAX);
>
> - bo = xe_managed_bo_create_pin_map(xe, tile, um_size,
> - XE_BO_FLAG_SYSTEM |
> - XE_BO_FLAG_GGTT |
> - XE_BO_FLAG_GGTT_INVALIDATE |
> - XE_BO_FLAG_PINNED_NORESTORE);
> + u32 um_flags = XE_BO_FLAG_VRAM_IF_DGFX(tile) |
> + XE_BO_FLAG_GGTT |
> + XE_BO_FLAG_GGTT_INVALIDATE |
> + XE_BO_FLAG_PINNED_NORESTORE;
> +
> + bo = xe_managed_bo_create_pin_map(xe, tile, um_size, um_flags);
> if (IS_ERR(bo))
> return PTR_ERR(bo);
>
next prev parent reply other threads:[~2026-08-04 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 20:08 [PATCH v7 0/1] drm/xe/guc_ads: allocate UM queues in a separate UC BO Jia Yao
2026-08-03 20:08 ` [PATCH v7 1/3] drm/xe/guc_ads: allocate UM queues in a separate BO Jia Yao
2026-08-04 7:43 ` Matthew Auld
2026-08-04 8:00 ` Matthew Auld
2026-08-04 8:54 ` Matthew Brost
2026-08-04 9:16 ` Matthew Auld
2026-08-04 9:25 ` Matthew Brost
2026-08-04 9:36 ` Matthew Auld
2026-08-03 20:08 ` [PATCH v7 2/3] drm/xe/guc_ads: allocate UM queues in VRAM on dGFX Jia Yao
2026-08-04 7:45 ` Matthew Auld [this message]
2026-08-03 20:08 ` [PATCH v7 3/3] drm/xe/guc_ads: use uncached mapping for UM queue BO Jia Yao
2026-08-03 20:15 ` ✓ CI.KUnit: success for drm/xe/guc_ads: allocate UM queues in a separate UC BO (rev5) Patchwork
2026-08-03 22:41 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-04 12:23 ` ✓ CI.KUnit: " 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=0a0db7a1-a3ad-45a3-9b59-723d539fbe88@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