On Wed, Jan 30, 2013 at 5:52 AM, Rob Clark wrote:
> On Wed, Jan 30, 2013 at 5:08 AM, Daniel Vetter wrote:
>> On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark wrote:
>>> ==
>>> Basic problem statement:
>>> - --- -
>>> GPU's do operations that commonly involve
On Wed, Jan 30, 2013 at 5:52 AM, Rob Clark robdcl...@gmail.com wrote:
On Wed, Jan 30, 2013 at 5:08 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark robdcl...@gmail.com wrote:
==
Basic problem statement:
- --- -
GPU's
Op 30-01-13 02:07, Rob Clark schreef:
> On Tue, Jan 15, 2013 at 6:33 AM, Maarten Lankhorst
> wrote:
> Hi Maarten,
>
> This is a nice looking extension to avoid re-implementing a mutex in
> TTM/reservation code.. ofc, probably someone more familiar with mutex
> code should probably review, but
On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark wrote:
> ==
> Basic problem statement:
> - --- -
> GPU's do operations that commonly involve many buffers. Those buffers
> can be shared across contexts/processes, exist in different memory
> domains (for example
On Wed, Jan 30, 2013 at 5:08 AM, Daniel Vetter wrote:
> On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark wrote:
>> ==
>> Basic problem statement:
>> - --- -
>> GPU's do operations that commonly involve many buffers. Those buffers
>> can be shared across
On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark robdcl...@gmail.com wrote:
==
Basic problem statement:
- --- -
GPU's do operations that commonly involve many buffers. Those buffers
can be shared across contexts/processes, exist in different memory
domains
Op 30-01-13 02:07, Rob Clark schreef:
On Tue, Jan 15, 2013 at 6:33 AM, Maarten Lankhorst
m.b.lankho...@gmail.com wrote:
Hi Maarten,
This is a nice looking extension to avoid re-implementing a mutex in
TTM/reservation code.. ofc, probably someone more familiar with mutex
code should
On Wed, Jan 30, 2013 at 5:08 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jan 30, 2013 at 2:07 AM, Rob Clark robdcl...@gmail.com wrote:
==
Basic problem statement:
- --- -
GPU's do operations that commonly involve many buffers. Those buffers
can
On Tue, Jan 15, 2013 at 6:33 AM, Maarten Lankhorst
wrote:
>
Hi Maarten,
This is a nice looking extension to avoid re-implementing a mutex in
TTM/reservation code.. ofc, probably someone more familiar with mutex
code should probably review, but probably a bit of explanation about
what and why
On Tue, Jan 15, 2013 at 6:33 AM, Maarten Lankhorst
m.b.lankho...@gmail.com wrote:
Hi Maarten,
This is a nice looking extension to avoid re-implementing a mutex in
TTM/reservation code.. ofc, probably someone more familiar with mutex
code should probably review, but probably a bit of
Woops, missed the updated patch description..
Op 15-01-13 13:33, Maarten Lankhorst schreef:
> makes it easier to port ttm over..
>
> Signed-off-by: Maarten Lankhorst
mutex_reserve_lock, and mutex_reserve_lock_interruptible:
Lock a buffer with a reservation_id set. reservation_id must not be
makes it easier to port ttm over..
Signed-off-by: Maarten Lankhorst
---
include/linux/mutex.h | 86 +-
kernel/mutex.c| 317 +++---
2 files changed, 387 insertions(+), 16 deletions(-)
diff --git a/include/linux/mutex.h
makes it easier to port ttm over..
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
---
include/linux/mutex.h | 86 +-
kernel/mutex.c| 317 +++---
2 files changed, 387 insertions(+), 16 deletions(-)
diff --git
Woops, missed the updated patch description..
Op 15-01-13 13:33, Maarten Lankhorst schreef:
makes it easier to port ttm over..
Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com
mutex_reserve_lock, and mutex_reserve_lock_interruptible:
Lock a buffer with a reservation_id set.
14 matches
Mail list logo
