AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@amd.com>,
	amd-gfx@lists.freedesktop.org
Cc: Alexander.Deucher@amd.com
Subject: Re: [Patch v1 4/5] drm/amdkfd: show warning when kfd is locked
Date: Tue, 28 Jan 2020 17:42:12 -0500	[thread overview]
Message-ID: <5209ef6a-693a-db6c-4ed2-6f234cc00a14@amd.com> (raw)
In-Reply-To: <20200128012923.25536-5-rajneesh.bhardwaj@amd.com>

On 2020-01-27 20:29, Rajneesh Bhardwaj wrote:
> During system suspend the kfd driver aquires a lock that prohibits
> further kfd actions unless the gpu is resumed. This adds some info which
> can be useful while debugging.
>
> Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@amd.com>
> ---
>   drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> index 1aebda4bbbe7..081cc5f40d18 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_chardev.c
> @@ -127,6 +127,8 @@ static int kfd_open(struct inode *inode, struct file *filep)
>   		return PTR_ERR(process);
>   
>   	if (kfd_is_locked()) {
> +		dev_warn(kfd_device, "kfd is locked!\n"
> +				"process %d unreferenced", process->pasid);

If this is for debugging, make it dev_dbg. Printing warnings like this 
usually confuses people reporting completely unrelated problems that 
aren't even kernel problems at all. "Look, I found a warning in the 
kernel log. It must be a kernel problem."

Regards,
   Felix


>   		kfd_unref_process(process);
>   		return -EAGAIN;
>   	}
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-01-28 22:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  1:29 [Patch v1 0/5] Enable BACO with KFD Rajneesh Bhardwaj
2020-01-28  1:29 ` [Patch v1 1/5] drm/amdgpu: always enable runtime power management Rajneesh Bhardwaj
2020-01-28 20:14   ` Alex Deucher
2020-01-30 19:06     ` Bhardwaj, Rajneesh
2020-01-28  1:29 ` [Patch v1 2/5] drm/amdgpu: Fix missing error check in suspend Rajneesh Bhardwaj
2020-01-28 20:15   ` Alex Deucher
2020-01-28  1:29 ` [Patch v1 3/5] drm/amdkfd: Introduce debugfs option to disable baco Rajneesh Bhardwaj
2020-01-28 20:22   ` Alex Deucher
2020-01-30 19:05     ` Bhardwaj, Rajneesh
2020-01-28  1:29 ` [Patch v1 4/5] drm/amdkfd: show warning when kfd is locked Rajneesh Bhardwaj
2020-01-28 22:42   ` Felix Kuehling [this message]
2020-01-30 19:02     ` Bhardwaj, Rajneesh
2020-01-28  1:29 ` [Patch v1 5/5] drm/amdkfd: refactor runtime pm for baco Rajneesh Bhardwaj
2020-01-28 20:09   ` Zeng, Oak
2020-01-30 19:08     ` Bhardwaj, Rajneesh
2020-01-29 22:52   ` Felix Kuehling
2020-01-30 19:01     ` Bhardwaj, Rajneesh
2020-01-30 21:55       ` Felix Kuehling
2020-01-30 22:11         ` Alex Deucher
2020-01-30 23:24           ` Felix Kuehling
2020-01-31  0:53             ` Zeng, Oak
2020-01-28 17:39 ` [Patch v1 0/5] Enable BACO with KFD Mike Lothian
2020-01-28 20:11   ` Alex Deucher

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=5209ef6a-693a-db6c-4ed2-6f234cc00a14@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=rajneesh.bhardwaj@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