From: "Paneer Selvam, Arunpravin" <arunpravin.paneerselvam@amd.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Cc: "Michel Dänzer" <mdaenzer@redhat.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu: always allocate cleared VRAM for GEM allocations
Date: Thu, 29 Aug 2024 23:39:22 +0530 [thread overview]
Message-ID: <c52a3df8-dcad-4fc7-8051-b8a05e1b49f2@amd.com> (raw)
In-Reply-To: <20240829172645.1678920-1-alexander.deucher@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
this will fix performance issues,
Acked-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com
<mailto:Arunpravin.PaneerSelvam@amd.com>>
On 8/29/2024 10:56 PM, Alex Deucher wrote:
> This adds allocation latency, but aligns better with user
> expectations. The latency should improve with the drm buddy
> clearing patches that Arun has been working on.
>
> In addition this fixes the high CPU spikes seen when doing
> wipe on release.
>
> v2: always set AMDGPU_GEM_CREATE_VRAM_CLEARED (Christian)
>
> Closes:https://gitlab.freedesktop.org/drm/amd/-/issues/3528
> Fixes: a68c7eaa7a8f ("drm/amdgpu: Enable clear page functionality")
> Reviewed-by: Michel Dänzer<mdaenzer@redhat.com> (v1)
> Signed-off-by: Alex Deucher<alexander.deucher@amd.com>
> Cc: Arunpravin Paneer Selvam<Arunpravin.PaneerSelvam@amd.com>
> Cc: Christian König<christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
> index 1f149c9e2177..8794661b0bfa 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
> @@ -349,6 +349,9 @@ int amdgpu_gem_create_ioctl(struct drm_device *dev, void *data,
> return -EINVAL;
> }
>
> + /* always clear VRAM */
> + flags |= AMDGPU_GEM_CREATE_VRAM_CLEARED;
> +
> /* create a gem object to contain this object in */
> if (args->in.domains & (AMDGPU_GEM_DOMAIN_GDS |
> AMDGPU_GEM_DOMAIN_GWS | AMDGPU_GEM_DOMAIN_OA)) {
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2024-08-29 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 17:26 [PATCH] drm/amdgpu: always allocate cleared VRAM for GEM allocations Alex Deucher
2024-08-29 18:09 ` Paneer Selvam, Arunpravin [this message]
2024-09-06 14:07 ` Marek Olšák
2024-09-06 17:53 ` Alex Deucher
2024-09-06 18:50 ` Marek Olšák
2024-09-10 6:10 ` Paneer Selvam, Arunpravin
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 13:36 Alex Deucher
2024-08-23 14:01 ` Christian König
2024-07-26 13:41 Alex Deucher
2024-07-26 15:25 ` Alex Deucher
2024-07-29 10:42 ` Michel Dänzer
2024-07-29 11:14 ` Christian König
2024-07-29 15:41 ` Michel Dänzer
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=c52a3df8-dcad-4fc7-8051-b8a05e1b49f2@amd.com \
--to=arunpravin.paneerselvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=mdaenzer@redhat.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