linux-kernel - Re:Re: [PATCH] drm/amdgpu: Reduce a lock scope in amdgpu_amdkfd_gpuvm_free_memory_of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AJ6AmADaCLivAKtTLreYUqof.3.1587343914555.Hmail.bernard@vivo.com>
Date:   Mon, 20 Apr 2020 08:51:54 +0800 (GMT+08:00)
From:   赵军奎 <bernard@...o.com>
To:     Markus Elfring <Markus.Elfring@....de>
Cc:     amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
        Alex Deucher <alexander.deucher@....com>,
        Christian König <christian.koenig@....com>,
        Chunming Zhou <David1.Zhou@....com>,
        Felix Kühling <Felix.Kuehling@....com>,
        kernel@...o.com, linux-kernel@...r.kernel.org,
        Daniel Vetter <daniel@...ll.ch>,
        David Airlie <airlied@...ux.ie>
Subject: Re:Re: [PATCH] drm/amdgpu: Reduce a lock scope in amdgpu_amdkfd_gpuvm_free_memory_of_gpu()



From: Markus Elfring <Markus.Elfring@....de>
Date: 2020-04-19 17:05:07
To:  Bernard Zhao <bernard@...o.com>,amd-gfx@...ts.freedesktop.org,dri-devel@...ts.freedesktop.org,Alex Deucher <alexander.deucher@....com>,"Christian König" <christian.koenig@....com>,Chunming Zhou <David1.Zhou@....com>,"Felix Kühling" <Felix.Kuehling@....com>
Cc:  kernel@...o.com,linux-kernel@...r.kernel.org,Daniel Vetter <daniel@...ll.ch>,David Airlie <airlied@...ux.ie>
Subject: Re: [PATCH] drm/amdgpu: Reduce a lock scope in amdgpu_amdkfd_gpuvm_free_memory_of_gpu()>> Maybe we could reduce the mutex_lock(&mem->lock)`s protected code area,
>> and noneed to protect pr_debug.
>
>I suggest to improve the commit message.
>Would you like to adjust the patch subject?
>
>Do you imagine that data synchronisation should evolve in other ways?
>
>Regards,
>Markus

Sure, I will modify the code and adjust this patch subject. I will submit it again.