Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH 1/3] drm/xe: Allow vram bo allocations aligned to 64K
Date: Tue, 13 Feb 2024 17:28:02 -0500	[thread overview]
Message-ID: <Zcvs8gIiqOV2RHl0@intel.com> (raw)
In-Reply-To: <20240213212418.1309-2-michal.wajdeczko@intel.com>

On Tue, Feb 13, 2024 at 10:24:16PM +0100, Michal Wajdeczko wrote:
> While today we are getting vram allocations aligned to 64K as the
> XE_VRAM_FLAGS_NEED64K flag could be set, we shouldn't only rely on
> that flag and we should also allow caller to specify required 64K
> alignment explicitly.  Define new XE_BO_NEEDS_64K flag for that.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_bo.c | 3 ++-
>  drivers/gpu/drm/xe/xe_bo.h | 1 +
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index d6a193060cc0..9da8bf506ab0 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -1256,7 +1256,8 @@ struct xe_bo *___xe_bo_create_locked(struct xe_device *xe, struct xe_bo *bo,
>  
>  	if (flags & (XE_BO_CREATE_VRAM_MASK | XE_BO_CREATE_STOLEN_BIT) &&
>  	    !(flags & XE_BO_CREATE_IGNORE_MIN_PAGE_SIZE_BIT) &&
> -	    xe->info.vram_flags & XE_VRAM_FLAGS_NEED64K) {
> +	    ((xe->info.vram_flags & XE_VRAM_FLAGS_NEED64K) ||
> +	     (flags & XE_BO_NEEDS_64K))) {
>  		aligned_size = ALIGN(size, SZ_64K);
>  		if (type != ttm_bo_type_device)
>  			size = ALIGN(size, SZ_64K);
> diff --git a/drivers/gpu/drm/xe/xe_bo.h b/drivers/gpu/drm/xe/xe_bo.h
> index db4b2db6b073..657399b90429 100644
> --- a/drivers/gpu/drm/xe/xe_bo.h
> +++ b/drivers/gpu/drm/xe/xe_bo.h
> @@ -45,6 +45,7 @@
>  #define XE_BO_PAGETABLE			BIT(12)
>  #define XE_BO_NEEDS_CPU_ACCESS		BIT(13)
>  #define XE_BO_NEEDS_UC			BIT(14)
> +#define XE_BO_NEEDS_64K			BIT(15)
>  /* this one is trigger internally only */
>  #define XE_BO_INTERNAL_TEST		BIT(30)
>  #define XE_BO_INTERNAL_64K		BIT(31)
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-02-13 22:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 21:24 [PATCH 0/3] LMTT improvements Michal Wajdeczko
2024-02-13 21:24 ` [PATCH 1/3] drm/xe: Allow vram bo allocations aligned to 64K Michal Wajdeczko
2024-02-13 22:28   ` Rodrigo Vivi [this message]
2024-02-13 21:24 ` [PATCH 2/3] drm/xe/pf: Request 64K aligned allocations for LMTT PD Michal Wajdeczko
2024-02-13 22:27   ` Rodrigo Vivi
2024-02-13 21:24 ` [PATCH 3/3] drm/xe/pf: Always use Multi-Level LMTT for newer platforms Michal Wajdeczko
2024-02-13 22:30   ` Rodrigo Vivi
2024-02-13 22:23 ` ✓ CI.Patch_applied: success for LMTT improvements Patchwork
2024-02-13 22:23 ` ✓ CI.checkpatch: " Patchwork
2024-02-13 22:24 ` ✓ CI.KUnit: " Patchwork
2024-02-13 22:35 ` ✓ CI.Build: " Patchwork
2024-02-13 22:35 ` ✓ CI.Hooks: " Patchwork
2024-02-13 22:37 ` ✓ CI.checksparse: " Patchwork
2024-02-13 22:59 ` ✓ CI.BAT: " 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=Zcvs8gIiqOV2RHl0@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@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