From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>,
intel-xe@lists.freedesktop.org
Cc: himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH] drm/xe/client: bo->client does not need bos_lock
Date: Mon, 10 Feb 2025 14:12:06 +0100 [thread overview]
Message-ID: <a2a8a8a2-66c7-4a73-94c4-a9b11e83b404@linux.intel.com> (raw)
In-Reply-To: <20250205051042.1991192-1-tejas.upadhyay@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
RB-ed and merged to drm-xe-next.
Thanks
On 2/5/2025 6:10 AM, Tejas Upadhyay wrote:
> bos_lock is to protect list of bos used by client, it is
> not required to protect bo->client so bring it outside of
> bos_lock.
>
> Fixes: b27970f3e11c ("drm/xe: Add tracking support for bos per client")
> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> ---
> drivers/gpu/drm/xe/xe_drm_client.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_drm_client.c b/drivers/gpu/drm/xe/xe_drm_client.c
> index 63f30b6df70b..2d4874d2b922 100644
> --- a/drivers/gpu/drm/xe/xe_drm_client.c
> +++ b/drivers/gpu/drm/xe/xe_drm_client.c
> @@ -135,8 +135,8 @@ void xe_drm_client_add_bo(struct xe_drm_client *client,
> XE_WARN_ON(bo->client);
> XE_WARN_ON(!list_empty(&bo->client_link));
>
> - spin_lock(&client->bos_lock);
> bo->client = xe_drm_client_get(client);
> + spin_lock(&client->bos_lock);
> list_add_tail(&bo->client_link, &client->bos_list);
> spin_unlock(&client->bos_lock);
> }
prev parent reply other threads:[~2025-02-10 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 5:10 [PATCH] drm/xe/client: bo->client does not need bos_lock Tejas Upadhyay
2025-02-05 5:34 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-05 5:35 ` ✓ CI.checkpatch: " Patchwork
2025-02-05 5:36 ` ✓ CI.KUnit: " Patchwork
2025-02-05 5:52 ` ✓ CI.Build: " Patchwork
2025-02-05 5:54 ` ✓ CI.Hooks: " Patchwork
2025-02-05 5:56 ` ✓ CI.checksparse: " Patchwork
2025-02-05 6:15 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-05 11:50 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-07 5:44 ` [PATCH] " Ghimiray, Himal Prasad
2025-02-10 13:12 ` Nirmoy Das [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=a2a8a8a2-66c7-4a73-94c4-a9b11e83b404@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@intel.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 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.