AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
	amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, christian.koenig@amd.com, shane.xiao@amd.com
Subject: Re: [PATCH] Revert "drm/amdgpu: remove TOPDOWN flags when allocating VRAM in large bar system"
Date: Thu, 1 Jun 2023 16:40:00 +0200	[thread overview]
Message-ID: <bc744636-9eb0-0714-df77-cd058f8cfc28@gmail.com> (raw)
In-Reply-To: <20230520092518.1993-1-Arunpravin.PaneerSelvam@amd.com>

Am 20.05.23 um 11:25 schrieb Arunpravin Paneer Selvam:
> This reverts commit c105518679b6e87232874ffc989ec403bee59664.
>
> This patch disables the TOPDOWN flag for APU and few dGPU cards
> which has the VRAM size equal to the BAR size.
>
> When we enable the TOPDOWN flag, we get the free blocks at
> the highest available memory region and we don't split the
> lower order blocks. This change is required to keep off
> the fragmentation related issues particularly in ASIC
> which has VRAM space <= 500MiB
>
> Hence, we are reverting this patch.
>
> Gitlab issue link - https://gitlab.freedesktop.org/drm/amd/-/issues/2270
>
> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>

For now Reviewed-by: Christian König <christian.koenig@amd.com> for this 
change.

The extra overhead for the topdown handling is intentional here as far 
as I can see.

Christian.

> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> index 2bd1a54ee866..ca5fc07faf6c 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
> @@ -139,7 +139,7 @@ void amdgpu_bo_placement_from_domain(struct amdgpu_bo *abo, u32 domain)
>   
>   		if (flags & AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED)
>   			places[c].lpfn = visible_pfn;
> -		else if (adev->gmc.real_vram_size != adev->gmc.visible_vram_size)
> +		else
>   			places[c].flags |= TTM_PL_FLAG_TOPDOWN;
>   
>   		if (flags & AMDGPU_GEM_CREATE_VRAM_CONTIGUOUS)


      parent reply	other threads:[~2023-06-01 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-20  9:25 [PATCH] Revert "drm/amdgpu: remove TOPDOWN flags when allocating VRAM in large bar system" Arunpravin Paneer Selvam
2023-05-20 18:39 ` Felix Kuehling
2023-05-22  3:22   ` Xiao, Shane
2023-05-26 18:11     ` Arunpravin Paneer Selvam
2023-05-29  2:35       ` Xiao, Shane
2023-05-29  6:44         ` Arunpravin Paneer Selvam
2023-05-23 18:56   ` Arunpravin Paneer Selvam
2023-06-01 14:40 ` Christian König [this message]

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=bc744636-9eb0-0714-df77-cd058f8cfc28@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=shane.xiao@amd.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