From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Michał Winiarski" <michal.winiarski@intel.com>
Subject: Re: [PATCH 2/3] drm/xe/pf: Request 64K aligned allocations for LMTT PD
Date: Tue, 13 Feb 2024 17:27:49 -0500 [thread overview]
Message-ID: <Zcvs5ZPVcKv9Z4bW@intel.com> (raw)
In-Reply-To: <20240213212418.1309-3-michal.wajdeczko@intel.com>
On Tue, Feb 13, 2024 at 10:24:17PM +0100, Michal Wajdeczko wrote:
> Use explicit alignment flag to match hardware requirement.
Probably good to add here in the commit message:
"LMTT Directory must be aligned on a 64KB boundary in Local Memory,
as well as the directory entries for SRIOV."
or something like that.
But the patch itself looks correct to me.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Bspec: 52404, 67468
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> ---
> drivers/gpu/drm/xe/xe_lmtt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_lmtt.c b/drivers/gpu/drm/xe/xe_lmtt.c
> index 0d7c5514e092..dfb0e1887615 100644
> --- a/drivers/gpu/drm/xe/xe_lmtt.c
> +++ b/drivers/gpu/drm/xe/xe_lmtt.c
> @@ -71,7 +71,7 @@ static struct xe_lmtt_pt *lmtt_pt_alloc(struct xe_lmtt *lmtt, unsigned int level
> lmtt->ops->lmtt_pte_num(level)),
> ttm_bo_type_kernel,
> XE_BO_CREATE_VRAM_IF_DGFX(lmtt_to_tile(lmtt)) |
> - XE_BO_CREATE_PINNED_BIT);
> + XE_BO_NEEDS_64K | XE_BO_CREATE_PINNED_BIT);
> if (IS_ERR(bo)) {
> err = PTR_ERR(bo);
> goto out_free_pt;
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-02-13 22:27 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
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 [this message]
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=Zcvs5ZPVcKv9Z4bW@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@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.