Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/mm: WARN for unclean mm takedown
Date: Mon, 1 Jul 2013 20:09:07 -0700	[thread overview]
Message-ID: <20130701200907.00002569@unknown> (raw)
In-Reply-To: <1372708864-26963-3-git-send-email-daniel.vetter@ffwll.ch>

On Mon,  1 Jul 2013 22:01:04 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:

> The usual drm driver has tons of different drm_mm memory managers so
> the drm error message in dmesg is pretty useless. WARN instead so
> that we have the full backtrace.
> 
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

I've written this patch myself a number of times.
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>

> ---
>  drivers/gpu/drm/drm_mm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
> index f9d4873..d303e31 100644
> --- a/drivers/gpu/drm/drm_mm.c
> +++ b/drivers/gpu/drm/drm_mm.c
> @@ -699,8 +699,8 @@ void drm_mm_takedown(struct drm_mm * mm)
>  {
>  	struct drm_mm_node *entry, *next;
>  
> -	if (!list_empty(&mm->head_node.node_list)) {
> -		DRM_ERROR("Memory manager not clean. Delaying
> takedown\n");
> +	if (WARN(!list_empty(&mm->head_node.node_list),
> +		 "Memory manager not clean. Delaying takedown\n")) {
>  		return;
>  	}
>  

      reply	other threads:[~2013-07-02  3:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 20:01 [PATCH 1/3] drm/mm: fix debug table BUG Daniel Vetter
2013-07-01 20:01 ` [PATCH 2/3] drm/i915: Don't try to tear down the stolen drm_mm if it's not there Daniel Vetter
2013-07-01 20:13   ` Chris Wilson
2013-07-01 20:34     ` [PATCH] " Daniel Vetter
2013-07-02  7:54       ` Chris Wilson
2013-07-02  7:58         ` [Intel-gfx] " Daniel Vetter
2013-07-02  8:13           ` Chris Wilson
2013-07-02  8:41             ` Daniel Vetter
2013-07-02  8:48             ` Daniel Vetter
2013-07-02  9:25               ` Chris Wilson
2013-07-02  9:48                 ` Daniel Vetter
2013-07-02  7:59       ` Daniel Vetter
2013-07-01 20:01 ` [PATCH 3/3] drm/mm: WARN for unclean mm takedown Daniel Vetter
2013-07-02  3:09   ` Ben Widawsky [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=20130701200907.00002569@unknown \
    --to=ben@bwidawsk.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox