From: Yury Norov <ynorov@nvidia.com>
To: "Felix Kuehling" <Felix.Kuehling@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: use bitmap_clear() in amdgpu_amdkfd_device_init()
Date: Thu, 23 Apr 2026 21:27:21 -0400 [thread overview]
Message-ID: <aerG-e-D6wgs8gDl@yury> (raw)
In-Reply-To: <20260424005218.147961-1-ynorov@nvidia.com>
On Thu, Apr 23, 2026 at 08:52:17PM -0400, Yury Norov wrote:
> The bitmap_clear() works OK with both compile- and runtime nbits. But the
> comment says it doesn't work, and opencodes the call for nothing. Drop
> the misleading comment, and use bitmap_clear() as it should.
>
> As a side effect, the patch switches from a series of atomics to
> a single non-atomic operation, which is easier on caches.
>
> Signed-off-by: Yury Norov <ynorov@nvidia.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> index d9e283f3b57d..47d52cb2f1ba 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
> @@ -194,14 +194,11 @@ void amdgpu_amdkfd_device_init(struct amdgpu_device *adev)
> adev->gfx.mec_bitmap[0].queue_bitmap,
> AMDGPU_MAX_QUEUES);
>
> - /* According to linux/bitmap.h we shouldn't use bitmap_clear if
> - * nbits is not compile time constant
> - */
> last_valid_bit = 1 /* only first MEC can have compute queues */
> * adev->gfx.mec.num_pipe_per_mec
> * adev->gfx.mec.num_queue_per_pipe;
> - for (i = last_valid_bit; i < AMDGPU_MAX_QUEUES; ++i)
> - clear_bit(i, gpu_resources.cp_queue_bitmap);
Please disregard. This patch accidentally dropped a chunk removing 'i'
declaration. I'll resend shortly.
> + bitmap_clear(gpu_resources.cp_queue_bitmap, last_valid_bit,
> + AMDGPU_MAX_QUEUES - last_valid_bit);
>
> amdgpu_doorbell_get_kfd_info(adev,
> &gpu_resources.doorbell_physical_address,
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-04-24 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 0:52 [PATCH] drm/amdgpu: use bitmap_clear() in amdgpu_amdkfd_device_init() Yury Norov
2026-04-24 1:27 ` Yury Norov [this message]
2026-04-25 15:57 ` kernel test robot
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=aerG-e-D6wgs8gDl@yury \
--to=ynorov@nvidia.com \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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