From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Victor Zhao <Victor.Zhao@amd.com>, amd-gfx@lists.freedesktop.org
Cc: philip.yang@amd.com
Subject: Re: [PATCH] drm/amdkfd: remove extra use of volatile
Date: Tue, 22 Oct 2024 16:05:11 +0200 [thread overview]
Message-ID: <b5d78aae-efc0-4d81-b9bb-213ea598957e@gmail.com> (raw)
In-Reply-To: <20241022135307.3566557-1-Victor.Zhao@amd.com>
Am 22.10.24 um 15:53 schrieb Victor Zhao:
> as the adding of mb() should be sufficient in function unmap_queues_cpsch,
> remove the add of volatile type as recommended
>
> Signed-off-by: Victor Zhao <Victor.Zhao@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 2 +-
> drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
> index 5a318376203c..38c19dc8311d 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
> @@ -2048,7 +2048,7 @@ int amdkfd_fence_wait_timeout(struct device_queue_manager *dqm,
> {
> unsigned long end_jiffies = msecs_to_jiffies(timeout_ms) + jiffies;
> struct device *dev = dqm->dev->adev->dev;
> - volatile uint64_t *fence_addr = dqm->fence_addr;
> + uint64_t *fence_addr = dqm->fence_addr;
>
> while (*fence_addr != fence_value) {
> /* Fatal err detected, this response won't come */
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h
> index bddb169bb301..09ab36f8e8c6 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.h
> @@ -260,7 +260,7 @@ struct device_queue_manager {
> uint16_t vmid_pasid[VMID_NUM];
> uint64_t pipelines_addr;
> uint64_t fence_gpu_addr;
> - volatile uint64_t *fence_addr;
> + uint64_t *fence_addr;
> struct kfd_mem_obj *fence_mem;
> bool active_runlist;
> int sched_policy;
prev parent reply other threads:[~2024-10-22 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 13:53 [PATCH] drm/amdkfd: remove extra use of volatile Victor Zhao
2024-10-22 14:05 ` Alex Deucher
2024-10-22 14:05 ` 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=b5d78aae-efc0-4d81-b9bb-213ea598957e@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Victor.Zhao@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=philip.yang@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