From: Felix Kuehling <felix.kuehling@amd.com>
To: 1587181464-114215-1-git-send-email-bernard@vivo.com,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com, Bernard Zhao <bernard@vivo.com>
Subject: Re: [PATCH V2] amdgpu: optimization-- reduce noneed mutex_lock area
Date: Tue, 21 Apr 2020 00:20:29 -0400 [thread overview]
Message-ID: <16175fa0-4d9b-2de8-e708-22b373a6f7a4@amd.com> (raw)
In-Reply-To: <20200421022528.126437-1-bernard@vivo.com>
Hi Bernard,
Thank you for the patch. Please see some comments inline.
Am 2020-04-20 um 10:25 p.m. schrieb Bernard Zhao:
> Maybe we could reduce the mutex_lock(&mem->lock)`s protected code area,
> and noneed to protect pr_debug.
Typo: noneed -> no need
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
>
> Changes since V1:
> *commit message improve
>
> Link for V1:
> *https://lore.kernel.org/patchwork/patch/1226588/
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> index 327317c54f7c..3c3769e57174 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c
> @@ -1285,17 +1285,18 @@ int amdgpu_amdkfd_gpuvm_free_memory_of_gpu(
> struct bo_vm_reservation_context ctx;
> struct ttm_validate_buffer *bo_list_entry;
> int ret;
> + unsigned int mapped_to_gpu_memory;
>
> mutex_lock(&mem->lock);
> + mapped_to_gpu_memory = mem->mapped_to_gpu_memory;
> + mutex_unlock(&mem->lock);
>
> - if (mem->mapped_to_gpu_memory > 0) {
> + if (mapped_to_gpu_memory > 0) {
> pr_debug("BO VA 0x%llx size 0x%lx is still mapped.\n",
> mem->va, bo_size);
> - mutex_unlock(&mem->lock);
> return -EBUSY;
> }
>
> - mutex_unlock(&mem->lock);
> /* lock is not needed after this, since mem is unused and will
> * be freed anyway
> */
Please move this comment along with the mutex_unlock.
Regards,
Felix
prev parent reply other threads:[~2020-04-21 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 2:25 [PATCH V2] amdgpu: optimization-- reduce noneed mutex_lock area Bernard Zhao
2020-04-21 4:20 ` Felix Kuehling [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=16175fa0-4d9b-2de8-e708-22b373a6f7a4@amd.com \
--to=felix.kuehling@amd.com \
--cc=1587181464-114215-1-git-send-email-bernard@vivo.com \
--cc=David1.Zhou@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bernard@vivo.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opensource.kernel@vivo.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