Re: [RFC PATCH v3 02/11] cgroup: Add mechanism to register DRM devices

2019-06-26 Thread Kenny Ho
On Wed, Jun 26, 2019 at 5:04 PM Daniel Vetter wrote: > On Wed, Jun 26, 2019 at 10:37 PM Kenny Ho wrote: > > (sending again, I keep missing the reply-all in gmail.) > You can make it the default somewhere in the gmail options. Um... interesting, my option was actually not set (neither reply or

Re: [RFC PATCH v3 02/11] cgroup: Add mechanism to register DRM devices

2019-06-26 Thread Daniel Vetter
On Wed, Jun 26, 2019 at 10:37 PM Kenny Ho wrote: > (sending again, I keep missing the reply-all in gmail.) You can make it the default somewhere in the gmail options. (also resending, I missed that you didn't group-replied). On Wed, Jun 26, 2019 at 10:25 PM Kenny Ho wrote: > > On Wed, Jun 26,

Re: [RFC PATCH v3 02/11] cgroup: Add mechanism to register DRM devices

2019-06-26 Thread Kenny Ho
(sending again, I keep missing the reply-all in gmail.) On Wed, Jun 26, 2019 at 11:56 AM Daniel Vetter wrote: > > Why the separate, explicit registration step? I think a simpler design for > drivers would be that we set up cgroups if there's anything to be > controlled, and then for GEM drivers

Re: [RFC PATCH v3 02/11] cgroup: Add mechanism to register DRM devices

2019-06-26 Thread Daniel Vetter
On Wed, Jun 26, 2019 at 11:05:13AM -0400, Kenny Ho wrote: > Change-Id: I908ee6975ea0585e4c30eafde4599f87094d8c65 > Signed-off-by: Kenny Ho Why the separate, explicit registration step? I think a simpler design for drivers would be that we set up cgroups if there's anything to be controlled, and

[RFC PATCH v3 02/11] cgroup: Add mechanism to register DRM devices

2019-06-26 Thread Kenny Ho
Change-Id: I908ee6975ea0585e4c30eafde4599f87094d8c65 Signed-off-by: Kenny Ho --- include/drm/drm_cgroup.h | 24 include/linux/cgroup_drm.h | 10 kernel/cgroup/drm.c| 116 + 3 files changed, 150 insertions(+) create mode 100644