All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Francisco Jerez <currojerez@riseup.net>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer.
Date: Tue, 21 Sep 2010 21:35:25 +0200	[thread overview]
Message-ID: <20100921193525.GA2746@joi.lan> (raw)
In-Reply-To: <1285028115-5235-1-git-send-email-currojerez@riseup.net>

On Tue, Sep 21, 2010 at 02:15:15AM +0200, Francisco Jerez wrote:
> It makes sense for a BO to move after a process has requested
> exclusive RW access on it (e.g. because the BO used to be located in
> unmappable VRAM and we intercepted the CPU access from the fault
> handler).
> 
> If we let the ghost object inherit cpu_writers from the original
> object, ttm_bo_release_list() will raise a kernel BUG when the ghost
> object is destroyed. This can be reproduced with the nouveau driver on
> nv5x.
> 
> Reported-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> Signed-off-by: Francisco Jerez <currojerez@riseup.net>

After few hours of testing, I can say:
Tested-by: Marcin Slusarz <marcin.slusarz@gmail.com>

Thanks,
Marcin

      parent reply	other threads:[~2010-09-21 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  0:15 [PATCH] drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer Francisco Jerez
2010-09-21 15:32 ` Jerome Glisse
2010-09-21 19:35 ` Marcin Slusarz [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=20100921193525.GA2746@joi.lan \
    --to=marcin.slusarz@gmail.com \
    --cc=currojerez@riseup.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thellstrom@vmware.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.