search for: dir_init

...anilo Krummrich wrote: > > +#ifdef CONFIG_DEBUG_FS > > + /* > > + * Logging buffers in debugfs. The wrapper objects need to remain > > + * in memory until the dentry is deleted. > > + */ > > + struct dentry *dir; /* Parent dentry */ > > + struct dentry *dir_init; > > + struct dentry *dir_rm; > > + struct dentry *dir_intr; > > + struct dentry *dir_pmu; > > I think `dir` is confusing, maybe just `dent_*`? Or maybe just wrap all those in > a `struct { ... } debugfs;` and just name them `init`, `rm`, etc.? Ok, but I'm pretty su...

...e registry RPC */ > size_t registry_rpc_size; > + > +#ifdef CONFIG_DEBUG_FS > + /* > + * Logging buffers in debugfs. The wrapper objects need to remain > + * in memory until the dentry is deleted. > + */ > + struct dentry *dir; /* Parent dentry */ > + struct dentry *dir_init; > + struct dentry *dir_rm; > + struct dentry *dir_intr; > + struct dentry *dir_pmu; I think `dir` is confusing, maybe just `dent_*`? Or maybe just wrap all those in a `struct { ... } debugfs;` and just name them `init`, `rm`, etc.? > + struct debugfs_blob_wrapper blob_init; > + st...

...nction + * is called too late. We really want to create these debugfs entries before + * r535_gsp_booter_load() is called, so that if GSP-RM fails to initialize, + * there could still be a log to capture. + */ +static void +r535_gsp_libos_debugfs_init(struct nvkm_gsp *gsp) +{ + struct dentry *dir, *dir_init; + struct dentry *dir_intr = NULL, *dir_rm = NULL, *dir_pmu = NULL; + struct device *dev = gsp->subdev.device->dev; + + /* Each GPU has a subdir based on its device name, so find it */ + struct drm_device *drm_dev = dev_get_drvdata(dev); + + if (!drm_dev || !drm_dev->debugfs_root) { + nvk...

Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- v2: rebased to drm-misc-next

...eally want to create these debugfs entries before > + * r535_gsp_booter_load() is called, so that if GSP-RM fails to initialize, > + * there could still be a log to capture. > + */ > +static void > +r535_gsp_libos_debugfs_init(struct nvkm_gsp *gsp) > +{ > + struct dentry *dir, *dir_init; > + struct dentry *dir_intr = NULL, *dir_rm = NULL, *dir_pmu = NULL; > + struct device *dev = gsp->subdev.device->dev; > + > + /* Each GPU has a subdir based on its device name, so find it */ > + struct drm_device *drm_dev = dev_get_drvdata(dev); > + > + if (!drm_dev ||...

...osfs:DOSFS_FindUnixName /c/windows,system trace:dosfs:DOSFS_FindUnixName (/c/windows,system) -> system (SYSTEM) trace:dosfs:DOSFS_GetFullName returning /c/windows/system = C:\WINDOWS\SYSTEM trace:dosfs:DOSFS_GetFullName e:\ (last=1) trace:dosfs:DOSFS_GetFullName returning /tmp = E:\ trace:dosfs:DIR_Init WindowsDir = C:\WINDOWS (/c/windows) trace:dosfs:DIR_Init SystemDir = C:\WINDOWS\SYSTEM (/c/windows/system) trace:dosfs:DIR_Init TempDir = E:\ (/tmp) trace:dosfs:DIR_Init Path = c:\windows;c:\windows\system;e:\;e:\test;f:\ trace:dosfs:DIR_Init Cwd = X:\MNT\CTYCTR3\SYS\APPS\GRPWIS...

Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- Notes: v2: added get/put_device calls

Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> v2: added get/put_device calls ---

Store the struct device pointer used to allocate the DMA buffer in the nvkm_gsp_mem object. This allows nvkm_gsp_mem_dtor() to release the buffer without needing the nvkm_gsp. This is needed so that we can retain DMA buffers even after the nvkm_gsp object is deleted. Signed-off-by: Timur Tabi <ttabi at nvidia.com> --- .../gpu/drm/nouveau/include/nvkm/subdev/gsp.h | 1 +

...;,2,0xbfffca88,2048) 0009:trace:environ:SetEnvironmentVariableW (L"PATH" L"C:\\windows;C:\\windows\\system;X:\\;X:\\test;Y:\\") 0009:trace:environ:RtlSetEnvironmentVariable ((nil),L"PATH",L"C:\\windows;C:\\windows\\system;X:\\;X:\\test;Y:\\") 0009:trace:dosfs:DIR_Init Path = L"C:\\windows;C:\\windows\\system;X:\\;X:\\test;Y:\\" 0009:trace:environ:GetEnvironmentVariableW (L"TEMP" (nil) 0) 0009:trace:environ:RtlQueryEnvironmentVariable_U (null) L"TEMP" 0xbfffca1c 0009:trace:environ:SetEnvironmentVariableW (L"TEMP" L&qu...

...0-based index for the engine. The class ID is just some seemingly random number that distinguishes the various engines. Building RM involves a lot of pre-processing with config files to generate much of the code that is compiled, and these class IDs are one example. + i_size_write(d_inode(dir_init), gsp->blob_init.size); + i_size_write(d_inode(dir_intr), gsp->blob_intr.size); + i_size_write(d_inode(dir_rm), gsp->blob_rm.size); + i_size_write(d_inode(dir_pmu), gsp->blob_pmu.size); + + r535_gsp_msg_ntfy_add(gsp, 0x0000100C, r535_gsp_msg_libos_print, gsp...

...00. So "previous RPC version (if it exists)" < "new RPC version" <= "current VGPU version" at the time the RPC was created/updated. > > +static void > > +r535_gsp_libos_debugfs_init(struct nvkm_gsp *gsp) > > +{ > > + struct dentry *dir, *dir_init; > > + struct dentry *dir_intr = NULL, *dir_rm = NULL, *dir_pmu = NULL; > > + struct device *dev = gsp->subdev.device->dev; > > + > > + /* Each GPU has a subdir based on its device name, so find it */ > > + struct drm_device *drm_dev = dev_get_drvdata(dev); >...