dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: David Airlie <airlied@linux.ie>,
	etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/etnaviv: try harder to dump core
Date: Mon, 23 Jul 2018 10:38:56 +0200	[thread overview]
Message-ID: <1532335136.3163.89.camel@pengutronix.de> (raw)
In-Reply-To: <E1ffSRG-0002dg-1Q@rmk-PC.armlinux.org.uk>

Hi Russell,

Am Dienstag, den 17.07.2018, 17:02 +0100 schrieb Russell King:
> Try a bit harder to produce a devcoredump when things go wrong.  If we
> fail to allocate the memory for a dump including the actual bo contents,
> omit the bos and try again.  Capturing some information from the GPU is
> better than having no information.

Agreed. One nit below.

> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> ---
>  drivers/gpu/drm/etnaviv/etnaviv_dump.c | 30 ++++++++++++++++++++++--------
>  1 file changed, 22 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/etnaviv/etnaviv_dump.c b/drivers/gpu/drm/etnaviv/etnaviv_dump.c
> index 48aef6cf6a42..c9987bc38acc 100644
> --- a/drivers/gpu/drm/etnaviv/etnaviv_dump.c
> +++ b/drivers/gpu/drm/etnaviv/etnaviv_dump.c
> @@ -129,6 +129,7 @@ void etnaviv_core_dump(struct etnaviv_gpu *gpu)
> >  	unsigned int n_obj, n_bomap_pages;
> >  	size_t file_size, mmu_size;
> >  	__le64 *bomap, *bomap_start;
> > +	bool bos = true;
>  
> >  	/* Only catch the first event, or when manually re-armed */
> >  	if (!etnaviv_dump_core)
> @@ -137,6 +138,7 @@ void etnaviv_core_dump(struct etnaviv_gpu *gpu)
>  
> >  	mmu_size = etnaviv_iommu_dump_size(gpu->mmu);
>  
> +again:
> >  	/* We always dump registers, mmu, ring and end marker */
> >  	n_obj = 4;
> >  	n_bomap_pages = 0;
> @@ -159,9 +161,12 @@ void etnaviv_core_dump(struct etnaviv_gpu *gpu)
> >  			continue;
>  
> >  		obj = vram->object;
> > -		file_size += obj->base.size;
> >  		n_bomap_pages += obj->base.size >> PAGE_SHIFT;
> > -		n_obj++;
> +
> > +		if (bos) {
> > +			file_size += obj->base.size;
> > +			n_obj++;
> > +		}
> >  	}
>  
> >  	/* If we have any buffer objects, add a bomap object */
> @@ -177,6 +182,11 @@ void etnaviv_core_dump(struct etnaviv_gpu *gpu)
> >  	iter.start = __vmalloc(file_size, GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY,
> >  			       PAGE_KERNEL);
> >  	if (!iter.start) {
> > +		if (bos) {
> > +			dev_warn(gpu->dev, "devcoredump too big, trying without bos\n");
> > +			bos = false;
> > +			goto again;
> > +		}
> >  		dev_warn(gpu->dev, "failed to allocate devcoredump file\n");
> >  		return;
> >  	}
> @@ -234,14 +244,18 @@ void etnaviv_core_dump(struct etnaviv_gpu *gpu)
> >  				*bomap++ = cpu_to_le64(page_to_phys(*pages++));
> >  		}
>  
> > -		iter.hdr->iova = cpu_to_le64(vram->iova);
> > +		if (bos) {
> > +			iter.hdr->iova = cpu_to_le64(vram->iova);
>  
> > -		vaddr = etnaviv_gem_vmap(&obj->base);
> > -		if (vaddr)
> > -			memcpy(iter.data, vaddr, obj->base.size);
> > +			vaddr = etnaviv_gem_vmap(&obj->base);
> > +			dev_crit(gpu->dev, "Copying object %p ops %pS vaddr %p to %p size %zu\n",
> +				obj, obj->ops, vaddr, iter.data, obj->base.size);

Did you mean to include this output in the patch? I guess it makes the
etnaviv coredump much more noisy in the system logs and doesn't carry
much useful info for the regular user.

Regards,
Lucas

> +			if (vaddr)
> > +				memcpy(iter.data, vaddr, obj->base.size);
>  
> > -		etnaviv_core_dump_header(&iter, ETDUMP_BUF_BO, iter.data +
> > -					 obj->base.size);
> > +			etnaviv_core_dump_header(&iter, ETDUMP_BUF_BO, iter.data +
> > +						 obj->base.size);
> > +		}
> >  	}
>  
> >  	etnaviv_core_dump_header(&iter, ETDUMP_BUF_END, iter.data);
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2018-07-23  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 16:02 [PATCH] drm/etnaviv: try harder to dump core Russell King
2018-07-23  8:38 ` Lucas Stach [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=1532335136.3163.89.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=rmk+kernel@armlinux.org.uk \
    /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