Searched refs:views (Results 1 – 11 of 11) sorted by relevance
340 memset(rc->views, 0, DEBUG_MAX_VIEWS * sizeof(struct debug_view *)); in debug_info_copy() 755 if (!debug_info->views[i]) in debug_dump() 765 p_info = debug_file_private_alloc(debug_info, debug_info->views[i]); in _debug_register() 1002 if (!id->views[i]) in debug_set_level() 1449 if (!id->views[i]) in debug_prolog_pages_fn() 1455 id->views[i] = view;1461 "number of views %i\n", id->name, view->name, i); in debug_input_pages_fn() 1490 if (id->views[i] == view) in debug_input_pages_fn() 1497 id->views[i] = NULL;1536 * functions for debug-views in debug_input_level_fn() [all...]
21 #define DEBUG_MAX_VIEWS 10 /* max number of views in proc fs */60 struct debug_view *views[DEBUG_MAX_VIEWS]; member 455 .views = { NULL }, \
203 struct vmw_ctx_bindinfo_view views[SVGA3D_DX11_1_MAX_UAVIEWS]; member
33 world views need to be described in a single device tree.
123 Some views generated by the debug feature to hold various debug outputs.
31 The S/390 debug feature (s390dbf) generates views to hold various debug results
763 u32 views; member
219 In general perf report output consist of 2 basic views:
24 different implementations of the same architecture have different views
1844 view = scene.views()[0]1851 view = scene.views()[0]
6258 both virtual and physical counter views (similar to the effects of the