Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Dugast <francois.dugast@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Allocate PF queue size on pow2 boundary
Date: Thu, 3 Jul 2025 09:22:38 +0200	[thread overview]
Message-ID: <aGYvvju-a3xoh2bM@fdugast-desk> (raw)
In-Reply-To: <20250702213511.3226167-1-matthew.brost@intel.com>

On Wed, Jul 02, 2025 at 02:35:11PM -0700, Matthew Brost wrote:
> CIRC_SPACE does not work unless the size argument is a power of 2,
> allocate PF queue size on power of 2 boundary.
> 
> Cc: stable@vger.kernel.org
> Fixes: 3338e4f90c14 ("drm/xe: Use topology to determine page fault queue size")
> Fixes: 29582e0ea75c ("drm/xe: Add page queue multiplier")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

This solves the issue I was seeing, thanks.

Reviewed-by: Francois Dugast <francois.dugast@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_gt_pagefault.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_pagefault.c b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> index 3522865c67c9..5a75d56d8558 100644
> --- a/drivers/gpu/drm/xe/xe_gt_pagefault.c
> +++ b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> @@ -419,6 +419,7 @@ static int xe_alloc_pf_queue(struct xe_gt *gt, struct pf_queue *pf_queue)
>  #define PF_MULTIPLIER	8
>  	pf_queue->num_dw =
>  		(num_eus + XE_NUM_HW_ENGINES) * PF_MSG_LEN_DW * PF_MULTIPLIER;
> +	pf_queue->num_dw = roundup_pow_of_two(pf_queue->num_dw);
>  #undef PF_MULTIPLIER
>  
>  	pf_queue->gt = gt;
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2025-07-03  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 21:35 [PATCH] drm/xe: Allocate PF queue size on pow2 boundary Matthew Brost
2025-07-02 21:39 ` ✓ CI.KUnit: success for " Patchwork
2025-07-02 22:47 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-03  7:22 ` Francois Dugast [this message]
2025-07-04 13:03 ` ✗ Xe.CI.Full: failure " 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=aGYvvju-a3xoh2bM@fdugast-desk \
    --to=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox