From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Nirmoy <nirmodas@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/amd/pm: drop unnecessary feature->mutex lock protections(V2)
Date: Fri, 28 Aug 2020 10:16:44 +0200 [thread overview]
Message-ID: <92deaaac-9ac5-8005-7070-2965367701b6@gmail.com> (raw)
In-Reply-To: <efc66f15-2291-dcdf-79eb-ce2085614360@amd.com>
The explanation sounds sane, but since I don't know the affected code at
all the series is only Acked-by: Christian König <christian.koenig@amd.com>
Maybe wait for Alex to give you an rb if you are unsure, otherwise feel
free to commit.
Christian.
Am 27.08.20 um 08:39 schrieb Nirmoy:
> Series is Acked-by: Nirmoy Das <nirmoy.das@amd.com>
>
>
> On 8/25/20 9:49 AM, Evan Quan wrote:
>> As these operations are performed in hardware setup and there
>> is actually no race conditions during this period considering:
>> 1. the hardware setup is serial and cannnot be in parallel
>> 2. all other operations can be performed only after hardware
>> setup complete.
>>
>> V2: rich the commit log description
>>
>> Change-Id: I096d7ab0855ff59b0ecb56fd9d6d9946b3605fc8
>> Signed-off-by: Evan Quan <evan.quan@amd.com>
>> ---
>> drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c | 4 ----
>> drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c | 2 --
>> 2 files changed, 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
>> b/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
>> index 09dc5303762b..b7cad8ef6153 100644
>> --- a/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
>> +++ b/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
>> @@ -361,20 +361,16 @@ static int
>> smu_get_driver_allowed_feature_mask(struct smu_context *smu)
>> int ret = 0;
>> uint32_t allowed_feature_mask[SMU_FEATURE_MAX/32];
>> - mutex_lock(&feature->mutex);
>> bitmap_zero(feature->allowed, SMU_FEATURE_MAX);
>> - mutex_unlock(&feature->mutex);
>> ret = smu_get_allowed_feature_mask(smu, allowed_feature_mask,
>> SMU_FEATURE_MAX/32);
>> if (ret)
>> return ret;
>> - mutex_lock(&feature->mutex);
>> bitmap_or(feature->allowed, feature->allowed,
>> (unsigned long *)allowed_feature_mask,
>> feature->feature_num);
>> - mutex_unlock(&feature->mutex);
>> return ret;
>> }
>> diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
>> b/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
>> index 548db1edd352..28a19ffd22a1 100644
>> --- a/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
>> +++ b/drivers/gpu/drm/amd/pm/swsmu/smu11/smu_v11_0.c
>> @@ -721,7 +721,6 @@ int smu_v11_0_set_allowed_mask(struct smu_context
>> *smu)
>> int ret = 0;
>> uint32_t feature_mask[2];
>> - mutex_lock(&feature->mutex);
>> if (bitmap_empty(feature->allowed, SMU_FEATURE_MAX) ||
>> feature->feature_num < 64)
>> goto failed;
>> @@ -738,7 +737,6 @@ int smu_v11_0_set_allowed_mask(struct
>> smu_context *smu)
>> goto failed;
>> failed:
>> - mutex_unlock(&feature->mutex);
>> return ret;
>> }
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-08-28 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 7:49 [PATCH 1/4] drm/amd/pm: drop unnecessary feature->mutex lock protections(V2) Evan Quan
2020-08-25 7:49 ` [PATCH 2/4] drm/amd/pm: drop unnecessary smu_baco->mutex " Evan Quan
2020-08-27 5:12 ` Quan, Evan
2020-08-25 7:49 ` [PATCH 3/4] drm/amd/pm: drop unnecessary table existence and dpm enablement check Evan Quan
2020-08-25 7:49 ` [PATCH 4/4] drm/amd/pm: minor cleanups Evan Quan
2020-08-27 5:12 ` [PATCH 1/4] drm/amd/pm: drop unnecessary feature->mutex lock protections(V2) Quan, Evan
2020-08-27 6:39 ` Nirmoy
2020-08-28 8:16 ` Christian König [this message]
2020-08-28 14:16 ` Deucher, Alexander
2020-08-31 7:01 ` Quan, Evan
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=92deaaac-9ac5-8005-7070-2965367701b6@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=nirmodas@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;
as well as URLs for NNTP newsgroup(s).