On 05/12/2012 01:48 PM, InKi Dae wrote:
> 2012/5/12 KOSAKI Motohiro :
>> On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
>>> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
>>> wrote:
> My point is this ioctl will be restricted to one user (Xserver if i
> understand) and only this
On 05/12/2012 01:48 PM, InKi Dae wrote:
> 2012/5/12 KOSAKI Motohiro :
>> On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
>>> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
>>> wrote:
> My point is this ioctl will be restricted to one user (Xserver if i
> understand) and only this
2012/5/12 KOSAKI Motohiro :
> On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
>> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
>> wrote:
My point is this ioctl will be restricted to one user (Xserver if i
understand) and only this user, there is no fork in it so no need to
On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
> wrote:
>>> My point is this ioctl will be restricted to one user (Xserver if i
>>> understand) and only this user, there is no fork in it so no need to
>>> worry about fork, just setting the
My point is this ioctl will be restricted to one user (Xserver if i
understand) and only this user, there is no fork in it so no need to
worry about fork, just setting the vma as locked will be enough.
But i don't want people reading this driver suddenly think that what
it's doing is ok, it's not
(5/10/12 11:01 PM), Jerome Glisse wrote:
On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
wrote:
(5/10/12 8:50 PM), Minchan Kim wrote:
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
let's assume that one application want to allocate user space memory
region using malloc() and
2012/5/12 KOSAKI Motohiro :
> On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
>> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
>> wrote:
My point is this ioctl will be restricted to one user (Xserver if i
understand) and only this user, there is no fork in it so no need to
On Fri, May 11, 2012 at 7:29 PM, Jerome Glisse wrote:
> On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
> wrote:
>>> My point is this ioctl will be restricted to one user (Xserver if i
>>> understand) and only this user, there is no fork in it so no need to
>>> worry about fork, just setting the
On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
wrote:
>> My point is this ioctl will be restricted to one user (Xserver if i
>> understand) and only this user, there is no fork in it so no need to
>> worry about fork, just setting the vma as locked will be enough.
>>
>> But i don't want people r
> My point is this ioctl will be restricted to one user (Xserver if i
> understand) and only this user, there is no fork in it so no need to
> worry about fork, just setting the vma as locked will be enough.
>
> But i don't want people reading this driver suddenly think that what
> it's doing is ok
On Fri, May 11, 2012 at 5:20 PM, KOSAKI Motohiro
wrote:
> (5/10/12 11:01 PM), Jerome Glisse wrote:
>>
>> On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
>> ?wrote:
>>>
>>> (5/10/12 8:50 PM), Minchan Kim wrote:
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>>
(5/10/12 11:01 PM), Jerome Glisse wrote:
> On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
> wrote:
>> (5/10/12 8:50 PM), Minchan Kim wrote:
>>>
>>> Hi KOSAKI,
>>>
>>> On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>>>
>>> let's assume that one application want to allocate user space memory
On Fri, May 11, 2012 at 6:59 PM, KOSAKI Motohiro
wrote:
>> My point is this ioctl will be restricted to one user (Xserver if i
>> understand) and only this user, there is no fork in it so no need to
>> worry about fork, just setting the vma as locked will be enough.
>>
>> But i don't want people r
On Fri, May 11, 2012 at 5:20 PM, KOSAKI Motohiro
wrote:
> (5/10/12 11:01 PM), Jerome Glisse wrote:
>>
>> On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
>> wrote:
>>>
>>> (5/10/12 8:50 PM), Minchan Kim wrote:
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>>
312.kim at samsung.com; dri-devel at lists.freedesktop.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Thu, May 10, 2012 at 11:31 AM, Daniel Vetter wrote:
>>> On Thu, May 10, 2012 at 11:05:07AM -0400, Jerome Glisse wrote:
>>
t; >> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
> >> >> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-
> mm at kvack.org
> >> >> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
> >> >>
> >&
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
let's assume that one application want to allocate user space memory
region using malloc() and then write something on the region. as you
may know, user space buffer doen't have real physical pages once
malloc() call so
(5/10/12 8:50 PM), Minchan Kim wrote:
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
let's assume that one application want to allocate user space memory
region using malloc() and then write something on the region. as you
may know, user space buffer doen't have real physical pages
t; sw0312@samsung.com; dri-devel@lists.freedesktop.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Thu, May 10, 2012 at 11:31 AM, Daniel Vetter wrote:
>>> On Thu, May 10, 2012 at 11:05:07AM -0400, Jerome Glisse wrote:
>>>> On Wed, May 9, 2012
Hi KOSAKI,
On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
let's assume that one application want to allocate user space memory
region using malloc() and then write something on the region. as you
may know, user space buffer doen't have real physical pages once
malloc() call so
let's assume that one application want to allocate user space memory
region using malloc() and then write something on the region. as you
may know, user space buffer doen't have real physical pages once
malloc() call so if user tries to access the region then page fault
handler would be triggered
On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
wrote:
> (5/10/12 8:50 PM), Minchan Kim wrote:
>>
>> Hi KOSAKI,
>>
>> On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>>
>> let's assume that one application want to allocate user space memory
>> region using malloc() and then write somethin
(5/10/12 8:50 PM), Minchan Kim wrote:
> Hi KOSAKI,
>
> On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>
> let's assume that one application want to allocate user space memory
> region using malloc() and then write something on the region. as you
> may know, user space buffer doen't have
On Thu, May 10, 2012 at 10:51 PM, KOSAKI Motohiro
wrote:
> (5/10/12 8:50 PM), Minchan Kim wrote:
>>
>> Hi KOSAKI,
>>
>> On 05/11/2012 02:53 AM, KOSAKI Motohiro wrote:
>>
>> let's assume that one application want to allocate user space memory
>> region using malloc() and then write somethin
> -Original Message-
> From: Jerome Glisse [mailto:j.gli...@gmail.com]
> Sent: Friday, May 11, 2012 12:53 AM
> To: Jerome Glisse; Inki Dae; linux...@kvack.org;
kyungmin.p...@samsung.com;
> sw0312@samsung.com; dri-devel@lists.freedesktop.org
> Subject: Re: [PATCH
sung.com; linux-mm at kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On 05/10/2012 04:59 PM, InKi Dae wrote:
>
> > 2012/5/10, Minchan Kim :
> >> On 05/10/2012 03:57 PM, Inki Dae wrote:
> >>
> >>>
> >>&
>> Sent: Thursday, May 10, 2012 3:33 AM
> >> To: Inki Dae
> >> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
> >> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
> >> kvack.org
> >> Subject: Re: [PATCH
rsday, May 10, 2012 1:58 PM
>>>> To: Inki Dae
>>>> Cc: 'Jerome Glisse'; airlied at linux.ie; dri-devel at
>>>> lists.freedesktop.org;
>>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>>> kvack.org
>> Cc: 'Jerome Glisse'; airlied at linux.ie; dri-devel at
>>> lists.freedesktop.org;
>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>> kvack.org
>>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>>
>>&
nesday, May 09, 2012 11:46 PM
>>>>>>> To: Inki Dae
>>>>>>> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
>>>>>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>>>>>> kvack.org
>>&g
linux.ie; dri-devel at lists.freedesktop.org;
>>>>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>>>>> kvack.org
>>>>>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>>>>>
>>&g
-
>>>>> From: Jerome Glisse [mailto:j.glisse at gmail.com]
>>>>> Sent: Wednesday, May 09, 2012 11:46 PM
>>>>> To: Inki Dae
>>>>> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
>>>>> kyungmin.park at samsung.com;
.com]
>>>> Sent: Wednesday, May 09, 2012 11:46 PM
>>>> To: Inki Dae
>>>> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
>>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>>> kvack.org
>>>> Sub
eedesktop.org;
>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>> kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On 05/10/2012 10:39 AM, Inki Dae wrote:
>>
>>> Hi Jerome,
>>>
>>
g.com; linux-mm at kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On 05/10/2012 10:39 AM, Inki Dae wrote:
>
> > Hi Jerome,
> >
> >> -Original Message-
> >> From: Jerome Glisse [mailto:j.glisse at gmail.com]
> >&g
org;
>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>> kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
>>> this feature is used to import user space reg
>>> let's assume that one application want to allocate user space memory
>>> region using malloc() and then write something on the region. as you
>>> may know, user space buffer doen't have real physical pages once
>>> malloc() call so if user tries to access the region then page fault
>>> handler
l Message-
>> >> From: Jerome Glisse [mailto:j.glisse at gmail.com]
>> >> Sent: Thursday, May 10, 2012 3:33 AM
>> >> To: Inki Dae
>> >> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
>> >> kyungmin.park at samsung.com
sung.com; linux-mm at kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
> > On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> >> this feature is used to import user space region allocated by
nux.ie; dri-devel at lists.freedesktop.org;
>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>> kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
>> > On Wed, M
ux-mm at kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> > this feature is used to import user space region allocated by malloc()
> or
> > mmaped into a gem. and to guarantee the pages to user
inal Message-
>> >> From: Jerome Glisse [mailto:j.gli...@gmail.com]
>> >> Sent: Thursday, May 10, 2012 3:33 AM
>> >> To: Inki Dae
>> >> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
>> >> kyungmin.p...@samsung.com; sw0312@sa
>> Sent: Thursday, May 10, 2012 3:33 AM
> >> To: Inki Dae
> >> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
> >> kyungmin.p...@samsung.com; sw0312....@samsung.com; linux...@kvack.org
> >> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
&
May 10, 2012 1:58 PM
>>>> To: Inki Dae
>>>> Cc: 'Jerome Glisse'; airl...@linux.ie; dri-devel@lists.freedesktop.org;
>>>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>>>> Subject: Re: [PATCH 2/2 v3] drm/exynos: ad
devel@lists.freedesktop.org;
>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
>> > On Wed, May 9, 2012 at 2:17
To: Inki Dae
>>> Cc: airlied at linux.ie; dri-devel at lists.freedesktop.org;
>>> kyungmin.park at samsung.com; sw0312.kim at samsung.com; linux-mm at
>>> kvack.org
>>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>>
>>> On Wed, May 9,
.@kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On 05/10/2012 04:59 PM, InKi Dae wrote:
>
> > 2012/5/10, Minchan Kim :
> >> On 05/10/2012 03:57 PM, Inki Dae wrote:
> >>
> >>>
> >>>
> >>>
Hi Jerome,
>>>>>
>>>>>> -Original Message-
>>>>>> From: Jerome Glisse [mailto:j.gli...@gmail.com]
>>>>>> Sent: Wednesday, May 09, 2012 11:46 PM
>>>>>> To: Inki Dae
>>>>>> Cc: airl...@linu
>>>> Sent: Wednesday, May 09, 2012 11:46 PM
>>>> To: Inki Dae
>>>> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
>>>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>>>> Subject: Re: [PATCH 2/2 v3] drm/ex
ktop.org;
>> kyungmin.p...@samsung.com; sw0312....@samsung.com; linux...@kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On 05/10/2012 10:39 AM, Inki Dae wrote:
>>
>>> Hi Jerome,
>>>
>>>> -Original Mes
...@samsung.com; sw0312@samsung.com; linux...@kvack.org
Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
this feature is used to import user space region allocated by malloc()
or
mmaped into a gem. and to guarantee the pages to user space
May 09, 2012 11:46 PM
>>>>>>> To: Inki Dae
>>>>>>> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
>>>>>>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>>>>>>> Subject: Re: [PATCH 2/2 v3] dr
27;Jerome Glisse'; airl...@linux.ie; dri-devel@lists.freedesktop.org;
>>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>>
>>> On 05/10/2012 10:39 AM, Inki Dae wrote:
&
>>>>> From: Jerome Glisse [mailto:j.gli...@gmail.com]
>>>>> Sent: Wednesday, May 09, 2012 11:46 PM
>>>>> To: Inki Dae
>>>>> Cc: airl...@linux.ie; dri-devel@lists.freedesktop.org;
>>>>> kyungmin.p...@samsung.com; sw0312
x...@kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On 05/10/2012 10:39 AM, Inki Dae wrote:
>
> > Hi Jerome,
> >
> >> -Original Message-
> >> From: Jerome Glisse [mailto:j.gli...@gmail.com]
> >> Sent: Wednesda
>> kyungmin.p...@samsung.com; sw0312@samsung.com; linux...@kvack.org
>> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>>
>> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
>>> this feature is used to import user space region allocated by malloc()
>
linux...@kvack.org
> Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
> > On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> >> this feature is used to import user space region allocated by malloc()
> or
; Subject: Re: [PATCH 2/2 v3] drm/exynos: added userptr feature.
>
> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> > this feature is used to import user space region allocated by malloc()
> or
> > mmaped into a gem. and to guarantee the pages to user space not to be
>
this feature is used to import user space region allocated by malloc() or
mmaped into a gem. and to guarantee the pages to user space not to be
swapped out, the VMAs within the user space would be locked and then unlocked
when the pages are released.
but this lock might result in significant degra
On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
>> this feature is used to import user space region allocated by malloc() or
>> mmaped into a gem. and to guarantee the pages to user space not to be
>> swapped out, the VMAs within the user sp
On Wed, May 9, 2012 at 10:45 AM, Jerome Glisse wrote:
> On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
>> this feature is used to import user space region allocated by malloc() or
>> mmaped into a gem. and to guarantee the pages to user space not to be
>> swapped out, the VMAs within the user sp
On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> this feature is used to import user space region allocated by malloc() or
> mmaped into a gem. and to guarantee the pages to user space not to be
> swapped out, the VMAs within the user space would be locked and then unlocked
> when the pages are r
On Wed, May 9, 2012 at 2:17 AM, Inki Dae wrote:
> this feature is used to import user space region allocated by malloc() or
> mmaped into a gem. and to guarantee the pages to user space not to be
> swapped out, the VMAs within the user space would be locked and then unlocked
> when the pages are r
this feature is used to import user space region allocated by malloc() or
mmaped into a gem. and to guarantee the pages to user space not to be
swapped out, the VMAs within the user space would be locked and then unlocked
when the pages are released.
but this lock might result in significant degra
64 matches
Mail list logo
