[RFC 4/4] drm/i915: Creating guc log file in drmfs instead of debugfs

2016-12-19 Thread swati.dhin...@intel.com
From: Sourab Gupta In the current scenario, the relay API fit well only with debugfs, due to availability of parent dentry. Any other existing filesystem was not feasible for holding guc logs, due to incompatibility with relay. But this makes the guc_log file unavailable on the production kerne

[RFC 3/4] drm: Create driver specific root directory inside drmfs

2016-12-19 Thread swati.dhin...@intel.com
From: Sourab Gupta A driver specific directory is created inside drmfs root, and dentry of this directory is saved for subsequent use by the driver (e.g. i915). The driver can then create files/directories inside this root directory directly. In case of i915 driver, the top directory is created

[RFC 2/4] drm: Register drmfs filesystem from drm init

2016-12-19 Thread swati.dhin...@intel.com
From: Sourab Gupta The drmfs filesystem will not be registered standalone during kernel init time, instead it is intended to be initialized/registered during drm initialization. This again is dependent on CONFIG_DRMFS being defined. Signed-off-by: Sourab Gupta Signed-off-by: Swati Dhingra ---

[RFC 1/4] drm: Introduce drmfs pseudo filesystem interfaces

2016-12-19 Thread swati.dhin...@intel.com
From: Sourab Gupta The patch introduces a new pseudo filesystem type, named 'drmfs' which is intended to house the files for the data generated by drm subsystem that cannot be accommodated by any of the existing filesystems. The filesystem is modelled on the lines of existing pseudo-filesystems s

[RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

2016-12-19 Thread swati.dhin...@intel.com
From: Swati Dhingra Currently, we don't have a stable ABI which can be used for the purpose of providing output debug/loggging/crc and other such data from DRM. The ABI in current use (filesystems, ioctls, et al.) have their own constraints and are intended to output a particular type of data. Fe

[RFC 4/4] drm/i915: Creating guc log file in drmfs instead of debugfs

2016-12-05 Thread swati.dhin...@intel.com
From: Sourab Gupta In the current scenario, the relay API fit well only with debugfs, due to availability of parent dentry. Any other existing filesystem was not feasible for holding guc logs, due to incompatibility with relay. But this makes the guc_log file unavailable on the production kerne

[RFC 3/4] drm: Create driver specific root directory inside drmfs

2016-12-05 Thread swati.dhin...@intel.com
From: Sourab Gupta A driver specific directory is created inside drmfs root, and dentry of this directory is saved for subsequent use by the driver (e.g. i915). The driver can then create files/directories inside this root directory directly. In case of i915 driver, the top directory is created

[RFC 2/4] drm: Register drmfs filesystem from drm init

2016-12-05 Thread swati.dhin...@intel.com
From: Sourab Gupta The drmfs filesystem will not be registered standalone during kernel init time, instead it is intended to be initialized/registered during drm initialization. Signed-off-by: Sourab Gupta Signed-off-by: Swati Dhingra --- drivers/gpu/drm/drm_drv.c | 6 ++ 1 file changed,

[RFC 1/4] drm: Introduce drmfs pseudo filesystem interfaces

2016-12-05 Thread swati.dhin...@intel.com
From: Sourab Gupta The patch introduces a new pseudo filesystem type, named 'drmfs' which is intended to house the files for the data generated by drm subsystem that cannot be accommodated by any of the existing filesystems. The filesystem is modelled on the lines of existing pseudo-filesystems s

[RFC 0/4] Introduce drmfs pseudo filesystem for drm subsystem

2016-12-05 Thread swati.dhin...@intel.com
From: Swati Dhingra Currently, we don't have a stable ABI which can be used for the purpose of providing output debug/loggging/crc and other such data from DRM. The ABI in current use (filesystems, ioctls, et al.) have their own constraints and are intended to output a particular type of data. Fe