[PATCH RFC 2/5] cgroup: Add mechanism to register vendor specific DRM devices

Ho, Kenny Kenny.Ho at amd.com
Tue Nov 20 22:21:14 UTC 2018

Hi Tejun,

Thanks for the reply.  A few clarifying questions:

On Tue, Nov 20, 2018 at 3:21 PM Tejun Heo <tj at kernel.org> 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 the best interest of
> everyone involved to keep it inside drm or specific driver proper.
By this reply, are you suggesting that vendor specific resources will never be acceptable to be managed under cgroup?  Let say a user want to have similar functionality as what cgroup is offering but to manage vendor specific resources, what would you suggest as a solution?  When you say keeping vendor specific resource regulation inside drm or specific drivers, do you mean we should replicate the cgroup infrastructure there or do you mean either drm or specific driver should query existing hierarchy (such as device or perhaps cpu) for the process organization information?

To put the questions in more concrete terms, let say a user wants to expose certain part of a gpu to a particular cgroup similar to the way selective cpu cores are exposed to a cgroup via cpuset, how should we go about enabling such functionality?


More information about the amd-gfx mailing list