[PATCH 5/5] drm: allocate kernel mode-object IDs in cyclic fashion

2015-09-11 Thread Daniel Vetter
On Fri, Sep 11, 2015 at 11:47 AM, David Herrmann wrote: > On Wed, Sep 9, 2015 at 3:03 PM, Daniel Vetter wrote: >> On Wed, Sep 09, 2015 at 02:21:33PM +0200, David Herrmann wrote: >>> Now that we support connector hotplugging, user-space might see >>> mode-object IDs coming and going asynchronousl

[PATCH 5/5] drm: allocate kernel mode-object IDs in cyclic fashion

2015-09-11 Thread David Herrmann
Hi On Wed, Sep 9, 2015 at 3:03 PM, Daniel Vetter wrote: > On Wed, Sep 09, 2015 at 02:21:33PM +0200, David Herrmann wrote: >> Now that we support connector hotplugging, user-space might see >> mode-object IDs coming and going asynchronously. Therefore, we must make >> sure to not re-use object IDs

[PATCH 5/5] drm: allocate kernel mode-object IDs in cyclic fashion

2015-09-09 Thread Daniel Vetter
On Wed, Sep 09, 2015 at 02:21:33PM +0200, David Herrmann wrote: > Now that we support connector hotplugging, user-space might see > mode-object IDs coming and going asynchronously. Therefore, we must make > sure to not re-use object IDs, so to not confuse user-space and introduce > races. Therefore

[PATCH 5/5] drm: allocate kernel mode-object IDs in cyclic fashion

2015-09-09 Thread David Herrmann
Now that we support connector hotplugging, user-space might see mode-object IDs coming and going asynchronously. Therefore, we must make sure to not re-use object IDs, so to not confuse user-space and introduce races. Therefore, all kernel-allocated objects will no longer recycle IDs. Instead, we u