Home
last modified time | relevance | path

Searched refs:views (Results 1 – 16 of 16) sorted by relevance

/kernel/linux/linux-5.10/arch/s390/kernel/
Ddebug.c254 memset(rc->views, 0, DEBUG_MAX_VIEWS * sizeof(struct debug_view *)); in debug_info_alloc()
540 if (!debug_info->views[i]) in debug_open()
555 if (!debug_info->views[i]->format_proc && !debug_info->views[i]->header_proc) in debug_open()
573 p_info->view = debug_info->views[i]; in debug_open()
701 if (!id->views[i]) in _debug_unregister()
1152 if (!id->views[i]) in debug_register_view()
1160 id->views[i] = view; in debug_register_view()
1192 if (id->views[i] == view) in debug_unregister_view()
1199 id->views[i] = NULL; in debug_unregister_view()
/kernel/linux/linux-5.10/Documentation/s390/
Ds390dbf.rst67 The content of the directories are files which represent different views
68 to the debug log. Each component can decide which views should be
70 Predefined views for hex/ascii and sprintf data are provided.
71 It is also possible to define other views. The content of
115 Predefined views:
214 See section about predefined views for explanation of the above output!
298 There are two predefined views: hex_ascii and sprintf.
341 Defining views
402 and which produces the same header output as the predefined views.
408 of the default views!
Dpci.rst30 The S/390 debug feature (s390dbf) generates views to hold various debug results in sysfs directorie…
Dcommon_io.rst123 Some views generated by the debug feature to hold various debug outputs.
/kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/
Dvmwgfx_binding.h203 struct vmw_ctx_bindinfo_view views[SVGA3D_MAX_UAVIEWS]; member
Dvmwgfx_binding.c203 offsetof(struct vmw_ctx_binding_state, ua_views[0].views),
206 offsetof(struct vmw_ctx_binding_state, ua_views[1].views),
1066 const struct vmw_ctx_bindinfo *loc = &cbs->ua_views[0].views[0].bi; in vmw_emit_set_uav()
1096 const struct vmw_ctx_bindinfo *loc = &cbs->ua_views[1].views[0].bi; in vmw_emit_set_cs_uav()
/kernel/linux/linux-5.10/arch/s390/include/asm/
Ddebug.h59 struct debug_view *views[DEBUG_MAX_VIEWS]; member
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dsecure.txt33 world views need to be described in a single device tree.
/kernel/linux/linux-5.10/Documentation/filesystems/
Derofs.rst104 may not. All metadatas can be now observed in two different spaces (views):
/kernel/linux/linux-5.10/drivers/media/platform/qcom/venus/
Dhfi_helper.h700 u32 views; member
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-c2c.txt164 In general perf report output consist of 2 basic views:
/kernel/linux/linux-5.10/Documentation/gpu/
Di915.rst428 Global GTT views
432 :doc: Global GTT views
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dconcepts.rst26 different implementations of the same architecture have different views
/kernel/linux/linux-5.10/tools/perf/scripts/python/
Dexported-sql-viewer.py1840 view = scene.views()[0]
1847 view = scene.views()[0]
/kernel/linux/linux-5.10/Documentation/process/
Dcoding-style.rst8 views on anybody, but this is what goes for anything that I have to be
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/
D0016_linux_drivers_crypto.patch6120 struct caam_deco __iomem *deco; /* DECO/CCB views */