is highly appreciated.
> >>>>
> >>>> Best Regards,
> >>>> Harish
> >>>>
> >>>>
> >>>>
> >>>> From: amd-gfx on behalf of Tejun
> >>>> Heo
> >>>> Sent: Tuesd
ciated.
>>>>
>>>> Best Regards,
>>>> Harish
>>>>
>>>>
>>>>
>>>> From: amd-gfx on behalf of Tejun
>>>> Heo
>>>> Sent: Tuesday, November 20, 2018 5:30 PM
>>>> To: Ho, Kenny
>>>
gt; > > > Your feedback is highly appreciated.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Harish
> > > > > > >
> > > > > > >
> > > > > > >
> Your feedback is highly appreciated.
> > > > > >
> > > > > > Best Regards,
> > > > > > Harish
> > > > > >
> > > > > >
> > > > > >
> > > > > > Fro
t; > > >
> > > > > Best Regards,
> > > > > Harish
> > > > >
> > > > >
> > > > >
> > > > > From: amd-gfx on behalf of
> > > > > Tejun Heo
> > > > > Sent: Tuesday, November 20, 20
> > >
> > > >
> > > > From: amd-gfx on behalf of
> > > > Tejun Heo
> > > > Sent: Tuesday, November 20, 2018 5:30 PM
> > > > To: Ho, Kenny
> > > > Cc: cgro...@vger.kernel.org; intel-...@lists.freedesktop.org;
gt; > > Heo
> > > Sent: Tuesday, November 20, 2018 5:30 PM
> > > To: Ho, Kenny
> > > Cc: cgro...@vger.kernel.org; intel-...@lists.freedesktop.org;
> > > y2ke...@gmail.com; amd-...@lists.freedesktop.org;
> > > dri-devel@lists.freedesktop.org
> > > Subj
m: amd-gfx on behalf of Tejun
> > Heo
> > Sent: Tuesday, November 20, 2018 5:30 PM
> > To: Ho, Kenny
> > Cc: cgro...@vger.kernel.org; intel-...@lists.freedesktop.org;
> > y2ke...@gmail.com; amd-...@lists.freedesktop.org;
> > dri-devel@lists.freedesktop.org
> >
el.org; intel-...@lists.freedesktop.org;
> y2ke...@gmail.com; amd-...@lists.freedesktop.org;
> dri-devel@lists.freedesktop.org
> Subject: Re: [PATCH RFC 2/5] cgroup: Add mechanism to register vendor
> specific DRM devices
>
>
> Hello,
>
> On Tue, Nov 20, 2018 at
reedesktop.org;
> dri-devel@lists.freedesktop.org
> Subject: Re: [PATCH RFC 2/5] cgroup: Add mechanism to register vendor
> specific DRM devices
>
>
> Hello,
>
> On Tue, Nov 20, 2018 at 10:21:14PM +, Ho, Kenny wrote:
>> By this reply, are you suggesting that
: [PATCH RFC 2/5] cgroup: Add mechanism to register vendor specific
DRM devices
Hello,
On Tue, Nov 20, 2018 at 10:21:14PM +, Ho, Kenny wrote:
> By this reply, are you suggesting that vendor specific resources
> will never be acceptable to be managed under cgroup? Let say a user
I wo
(resending because previous email switched to HTML mode and was filtered out)
Hi Tejun,
On Tue, Nov 20, 2018 at 5:30 PM Tejun Heo wrote:
> On Tue, Nov 20, 2018 at 10:21:14PM +, Ho, Kenny wrote:
> > By this reply, are you suggesting that vendor specific resources
> > will never be acceptable
Hi Tejun,
On Tue, Nov 20, 2018 at 5:30 PM Tejun Heo wrote:
> On Tue, Nov 20, 2018 at 10:21:14PM +, Ho, Kenny wrote:
> > By this reply, are you suggesting that vendor specific resources
> > will never be acceptable to be managed under cgroup? Let say a user
>
> I wouldn't say never but
Am 20.11.18 um 19:58 schrieb Kenny Ho:
Since many parts of the DRM subsystem has vendor-specific
implementations, we introduce mechanisms for vendor to register their
specific resources and control files to the DRM cgroup subsystem. A
vendor will register itself with the DRM cgroup subsystem
Hello,
On Tue, Nov 20, 2018 at 10:21:14PM +, Ho, Kenny wrote:
> By this reply, are you suggesting that vendor specific resources
> will never be acceptable to be managed under cgroup? Let say a user
I wouldn't say never but whatever which gets included as a cgroup
controller should have
Hi Tejun,
Thanks for the reply. A few clarifying questions:
On Tue, Nov 20, 2018 at 3:21 PM Tejun Heo wrote:
> So, I'm still pretty negative about adding drm controller at this
> point. There isn't enough of common resource model defined yet and
> until that gets sorted out I think it's in
Hello,
On Tue, Nov 20, 2018 at 01:58:11PM -0500, Kenny Ho wrote:
> Since many parts of the DRM subsystem has vendor-specific
> implementations, we introduce mechanisms for vendor to register their
> specific resources and control files to the DRM cgroup subsystem. A
> vendor will register itself
Since many parts of the DRM subsystem has vendor-specific
implementations, we introduce mechanisms for vendor to register their
specific resources and control files to the DRM cgroup subsystem. A
vendor will register itself with the DRM cgroup subsystem first before
registering individual DRM
18 matches
Mail list logo
