From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/nouveau: fix ttm move notify callback
Date: Fri, 6 Jan 2012 14:52:49 -0500 [thread overview]
Message-ID: <20120106195249.GA3213@phenom.dumpdata.com> (raw)
In-Reply-To: <20120106182220.GA2823@homer.localdomain>
> Still having difficulty to reproduce can you reproduce with the attached
> printk debuging patch and provide the log (only few printk preceding the
> oops or segfault are interesting).
http://darnok.org/vga/move_notify-v212.log
>
> Cheers,
> Jerome
> >From 862e2cc6d35d85404ed24d24c5a5c49c5ef45fc7 Mon Sep 17 00:00:00 2001
> From: Jerome Glisse <jglisse@redhat.com>
> Date: Fri, 6 Jan 2012 13:20:08 -0500
> Subject: [PATCH] TTM-DEBUG-PRINTK
>
> ---
> drivers/gpu/drm/nouveau/nouveau_bo.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c b/drivers/gpu/drm/nouveau/nouveau_bo.c
> index 724b41a..326b64a 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_bo.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_bo.c
> @@ -812,12 +812,14 @@ nouveau_bo_move_ntfy(struct ttm_buffer_object *bo, struct ttm_mem_reg *new_mem)
> struct nouveau_bo *nvbo = nouveau_bo(bo);
> struct nouveau_vma *vma;
>
> +DRM_INFO("%s list (%p %p)\n", __func__, nvbo->vma_list.prev, nvbo->vma_list.next);
> list_for_each_entry(vma, &nvbo->vma_list, head) {
> if (new_mem && new_mem->mem_type == TTM_PL_VRAM) {
> nouveau_vm_map(vma, new_mem->mm_node);
> } else
> if (new_mem && new_mem->mem_type == TTM_PL_TT &&
> nvbo->page_shift == vma->vm->spg_shift) {
> +DRM_INFO("%s vma %p new mem %p %d pages\n", __func__, vma, new_mem, new_mem->num_pages);
> nouveau_vm_map_sg(vma, 0, new_mem->
> num_pages << PAGE_SHIFT,
> new_mem->mm_node);
> --
> 1.7.5.4
>
next prev parent reply other threads:[~2012-01-06 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 18:31 [PATCH] drm/nouveau: fix ttm move notify callback j.glisse
2012-01-05 21:48 ` Konrad Rzeszutek Wilk
2012-01-05 21:51 ` Jerome Glisse
2012-01-05 21:53 ` Ben Skeggs
[not found] ` <20120106021410.GA3120@phenom.dumpdata.com>
2012-01-06 14:57 ` Konrad Rzeszutek Wilk
2012-01-06 16:51 ` Jerome Glisse
2012-01-06 16:53 ` Konrad Rzeszutek Wilk
2012-01-06 18:22 ` Jerome Glisse
2012-01-06 19:52 ` Konrad Rzeszutek Wilk [this message]
2012-01-06 21:00 ` Jerome Glisse
2012-01-10 3:46 ` Ben Skeggs
2012-01-10 14:34 ` Konrad Rzeszutek Wilk
2012-01-24 15:00 ` Konrad Rzeszutek Wilk
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=20120106195249.GA3213@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=jglisse@redhat.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.