All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdkfd: Ensure gpu_id is unique
Date: Tue, 7 May 2024 11:22:20 +0530	[thread overview]
Message-ID: <a50ee9ef-1a2a-4723-a638-936ac4e92653@amd.com> (raw)
In-Reply-To: <20240503220639.335198-1-Harish.Kasiviswanathan@amd.com>



On 5/4/2024 3:36 AM, Harish Kasiviswanathan wrote:
> gpu_id needs to be unique for user space to identify GPUs via KFD
> interface. In the current implementation there is a very small
> probability of having non unique gpu_ids.
> 
> v2: Add check to confirm if gpu_id is unique. If not unique, find one
>     Changed commit header to reflect the above
> 
> Signed-off-by: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
> ---
>  drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 26 ++++++++++++++++++++++-
>  1 file changed, 25 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index b93913934b03..01d4c2e10c6d 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -1095,6 +1095,8 @@ static uint32_t kfd_generate_gpu_id(struct kfd_node *gpu)
>  	uint32_t hashout;
>  	uint32_t buf[8];
>  	uint64_t local_mem_size;
> +	struct kfd_topology_device *dev;
> +	bool is_unique;
>  	int i;
>  
>  	if (!gpu)
> @@ -1115,6 +1117,28 @@ static uint32_t kfd_generate_gpu_id(struct kfd_node *gpu)
>  	for (i = 0, hashout = 0; i < 8; i++)
>  		hashout ^= hash_32(buf[i], KFD_GPU_ID_HASH_WIDTH);

Instead of this, suggest to replace this with crc16(). That has a better
chance to avoid collision as it takes into account the whole contents of
the buffer. It may work better than combining hashes with XOR.

Thanks,
Lijo

>  
> +	/* hash generated could be non-unique. Check if it is unique.
> +	 * If not unique increment till unique one is found. In case
> +	 * of overflow, restart from 1
> +	*/
> +	down_read(&topology_lock);
> +	do {
> +		is_unique = true;
> +		list_for_each_entry(dev, &topology_device_list, list) {
> +			if (dev->gpu && dev->gpu_id == hashout) {
> +				is_unique = false;
> +				break;
> +			}
> +		}
> +		if (unlikely(!is_unique)) {
> +			hashout = (hashout + 1) &
> +				  ((1 << KFD_GPU_ID_HASH_WIDTH) - 1);
> +			if (!hashout)
> +				hashout = 1;
> +		}
> +	} while (!is_unique);
> +	up_read(&topology_lock);
> +
>  	return hashout;
>  }
>  /* kfd_assign_gpu - Attach @gpu to the correct kfd topology device. If
> @@ -1946,7 +1970,6 @@ int kfd_topology_add_device(struct kfd_node *gpu)
>  	struct amdgpu_gfx_config *gfx_info = &gpu->adev->gfx.config;
>  	struct amdgpu_cu_info *cu_info = &gpu->adev->gfx.cu_info;
>  
> -	gpu_id = kfd_generate_gpu_id(gpu);
>  	if (gpu->xcp && !gpu->xcp->ddev) {
>  		dev_warn(gpu->adev->dev,
>  			 "Won't add GPU to topology since it has no drm node assigned.");
> @@ -1969,6 +1992,7 @@ int kfd_topology_add_device(struct kfd_node *gpu)
>  	if (res)
>  		return res;
>  
> +	gpu_id = kfd_generate_gpu_id(gpu);
>  	dev->gpu_id = gpu_id;
>  	gpu->id = gpu_id;
>  

  parent reply	other threads:[~2024-05-07  5:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 22:06 [PATCH] drm/amdkfd: Ensure gpu_id is unique Harish Kasiviswanathan
2024-05-06 20:30 ` Felix Kuehling
2024-05-06 21:10   ` Harish Kasiviswanathan
2024-05-06 22:14     ` Felix Kuehling
2024-05-07  5:52 ` Lazar, Lijo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 20:06 Harish Kasiviswanathan
2024-05-10 13:06 ` Lazar, Lijo
2024-05-10 20:57 ` Felix Kuehling

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=a50ee9ef-1a2a-4723-a638-936ac4e92653@amd.com \
    --to=lijo.lazar@amd.com \
    --cc=Harish.Kasiviswanathan@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.