From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 01/10] drm/radeon: allow move_notify to be called without reservation
Date: Mon, 12 Nov 2012 15:03:48 +0100 [thread overview]
Message-ID: <50A101C4.4090304@canonical.com> (raw)
In-Reply-To: <1352728811-21860-1-git-send-email-maarten.lankhorst@canonical.com>
Op 12-11-12 15:00, Maarten Lankhorst schreef:
> The few places that care should have those checks instead.
> This allow destruction of bo backed memory without a reservation.
Forgot to add, this patch series depends on the previous sync_obj_arg removal patches, and cpu_writers -EBUSY change.
~Maarten
prev parent reply other threads:[~2012-11-12 14:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 14:00 [PATCH 01/10] drm/radeon: allow move_notify to be called without reservation Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 02/10] drm/ttm: remove ttm_bo_cleanup_memtype_use Maarten Lankhorst
2012-11-19 13:26 ` Thomas Hellstrom
2012-11-19 14:03 ` Maarten Lankhorst
2012-11-19 14:12 ` Thomas Hellstrom
2012-11-12 14:00 ` [PATCH 03/10] drm/ttm: do not check if list is empty in ttm_bo_force_list_clean Maarten Lankhorst
2012-11-19 13:33 ` Thomas Hellstrom
2012-11-19 14:10 ` Maarten Lankhorst
2012-11-20 7:42 ` Thomas Hellstrom
2012-11-12 14:00 ` [PATCH 04/10] drm/ttm: change fence_lock to inner lock, v3 Maarten Lankhorst
2012-11-19 14:17 ` Thomas Hellstrom
2012-11-19 15:04 ` Thomas Hellstrom
2012-11-19 15:33 ` Maarten Lankhorst
2012-11-20 7:48 ` Thomas Hellstrom
2012-11-20 11:33 ` Maarten Lankhorst
2012-11-20 11:59 ` Maarten Lankhorst
2012-11-20 12:03 ` Thomas Hellstrom
2012-11-20 13:13 ` Maarten Lankhorst
2012-11-20 15:08 ` Thomas Hellstrom
2012-11-21 11:38 ` Maarten Lankhorst
2012-11-21 12:42 ` Thomas Hellstrom
2012-11-21 13:12 ` Maarten Lankhorst
2012-11-21 13:27 ` Thomas Hellstrom
2012-11-22 15:51 ` Maarten Lankhorst
2012-11-22 20:29 ` Thomas Hellstrom
2012-11-27 12:35 ` Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 05/10] drm/ttm: add sense to ttm_bo_cleanup_refs, v4 Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 06/10] drm/ttm: remove no_wait_reserve, v2 Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 07/10] drm/ttm: cope with reserved buffers on swap list in ttm_bo_swapout Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 08/10] drm/ttm: cope with reserved buffers on lru list in ttm_mem_evict_first Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 09/10] drm/ttm: remove lru_lock around ttm_bo_reserve Maarten Lankhorst
2012-11-12 14:00 ` [PATCH 10/10] drm/ttm: remove reliance on ttm_bo_wait_unreserved Maarten Lankhorst
2012-11-12 14:03 ` Maarten Lankhorst [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=50A101C4.4090304@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=m.b.lankhorst@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox