[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-10 Thread Daniel Vetter
On Thu, Jul 10, 2014 at 12:39:24AM +0900, Inki Dae wrote: > On 2014? 07? 09? 18:23, Daniel Vetter wrote: > > On Tue, Jul 8, 2014 at 6:20 PM, Inki Dae wrote: > >> 2014-07-08 22:37 GMT+09:00 Daniel Vetter : > >>> On Wed, Jul 02, 2014 at 11:25:19AM -0400, Jerome Glisse wrote: > Anyway as this

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-10 Thread Inki Dae
On 2014? 07? 09? 18:23, Daniel Vetter wrote: > On Tue, Jul 8, 2014 at 6:20 PM, Inki Dae wrote: >> 2014-07-08 22:37 GMT+09:00 Daniel Vetter : >>> On Wed, Jul 02, 2014 at 11:25:19AM -0400, Jerome Glisse wrote: Anyway as this is upstream i guess you can keep it. This is just an horrible

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-09 Thread Daniel Vetter
On Tue, Jul 8, 2014 at 6:20 PM, Inki Dae wrote: > 2014-07-08 22:37 GMT+09:00 Daniel Vetter : >> On Wed, Jul 02, 2014 at 11:25:19AM -0400, Jerome Glisse wrote: >>> Anyway as this is upstream i guess you can keep it. This is just an horrible >>> API that allow to circumvant any limit set by memcg

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-09 Thread Inki Dae
2014-07-08 22:37 GMT+09:00 Daniel Vetter : > On Wed, Jul 02, 2014 at 11:25:19AM -0400, Jerome Glisse wrote: >> Anyway as this is upstream i guess you can keep it. This is just an horrible >> API that allow to circumvant any limit set by memcg for page locking and all. >> But anyway GPU driver

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-08 Thread Daniel Vetter
On Wed, Jul 02, 2014 at 11:25:19AM -0400, Jerome Glisse wrote: > Anyway as this is upstream i guess you can keep it. This is just an horrible > API that allow to circumvant any limit set by memcg for page locking and all. > But anyway GPU driver never played in the same ballpark as other driver.

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-03 Thread Inki Dae
2014-07-02 0:03 GMT+09:00 Jerome Glisse : > On Tue, Jul 01, 2014 at 05:55:25PM +0900, Inki Dae wrote: >> >> Hi Jerome, >> >> >> On 2014? 07? 01? 06:46, j.glisse at gmail.com wrote: >> > From: Jerome Glisse >> > >> > get_user_pages gives no garanty that page it returns are still >> > the one

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-02 Thread Jerome Glisse
On Thu, Jul 03, 2014 at 12:09:25AM +0900, Inki Dae wrote: > 2014-07-02 0:03 GMT+09:00 Jerome Glisse : > > On Tue, Jul 01, 2014 at 05:55:25PM +0900, Inki Dae wrote: > >> > >> Hi Jerome, > >> > >> > >> On 2014? 07? 01? 06:46, j.glisse at gmail.com wrote: > >> > From: Jerome Glisse > >> > > >> >

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-01 Thread Inki Dae
Hi Jerome, On 2014? 07? 01? 06:46, j.glisse at gmail.com wrote: > From: Jerome Glisse > > get_user_pages gives no garanty that page it returns are still > the one backing the vma by the time it returns. Thus any ioctl One of pages from get_user_pages() could be migrated? I think all the

[PATCH] exynos: Put a stop to the userptr heresy.

2014-07-01 Thread Jerome Glisse
On Tue, Jul 01, 2014 at 05:55:25PM +0900, Inki Dae wrote: > > Hi Jerome, > > > On 2014? 07? 01? 06:46, j.glisse at gmail.com wrote: > > From: Jerome Glisse > > > > get_user_pages gives no garanty that page it returns are still > > the one backing the vma by the time it returns. Thus any ioctl

[PATCH] exynos: Put a stop to the userptr heresy.

2014-06-30 Thread j.gli...@gmail.com
From: Jerome Glisse get_user_pages gives no garanty that page it returns are still the one backing the vma by the time it returns. Thus any ioctl that rely on this behavior is broken and rely on pure luck. To avoid any false hope from userspace stop such useage by simply flat