All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Reduce verbosity on log overflows
Date: Mon, 17 Jun 2019 15:21:54 +0100	[thread overview]
Message-ID: <85dae10c-428f-eabf-93ca-4eded1253f12@linux.intel.com> (raw)
In-Reply-To: <20190617100917.13110-1-chris@chris-wilson.co.uk>


On 17/06/2019 11:09, Chris Wilson wrote:
> If the user is clearing the log buffer too slowly, we overflow. As this
> is an expected condition, and the driver tries to handle it, reduce the
> error message down to a notice.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110817
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
>   drivers/gpu/drm/i915/intel_guc_log.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_guc_log.c b/drivers/gpu/drm/i915/intel_guc_log.c
> index bf1446629703..e3b83ecb90b5 100644
> --- a/drivers/gpu/drm/i915/intel_guc_log.c
> +++ b/drivers/gpu/drm/i915/intel_guc_log.c
> @@ -208,7 +208,9 @@ static bool guc_check_log_buf_overflow(struct intel_guc_log *log,
>   			/* buffer_full_cnt is a 4 bit counter */
>   			log->stats[type].sampled_overflow += 16;
>   		}
> -		DRM_ERROR_RATELIMITED("GuC log buffer overflow\n");
> +
> +		dev_notice_ratelimited(guc_to_i915(log_to_guc(log))->drm.dev,
> +				       "GuC log buffer overflow\n");
>   	}
>   
>   	return overflow;
> 

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Maybe we could even go debug, although I not sure if userspace is 
expected to look at dmesg to detect overflows or if the thing has some 
marker it writes into the file in that case. I don't see it so that's 
probably a slight flaw.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-17 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 10:09 [PATCH] drm/i915/guc: Reduce verbosity on log overflows Chris Wilson
2019-06-17 14:21 ` Tvrtko Ursulin [this message]
2019-06-17 14:26   ` Chris Wilson
2019-06-17 14:38 ` Michal Wajdeczko
2019-06-17 14:42   ` Chris Wilson
2019-06-18 10:24   ` Chris Wilson
2019-06-18 10:30     ` Michal Wajdeczko
2019-06-17 17:36 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-18  4:48 ` ✗ Fi.CI.IGT: failure " Patchwork

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=85dae10c-428f-eabf-93ca-4eded1253f12@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-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.