Searched refs:timelines (Results 1 – 8 of 8) sorted by relevance
| /linux/tools/testing/selftests/sync/ |
| H A D | sync_stress_merge.c | 41 int timelines[timeline_count]; in test_merge_stress_random_merge() local 49 timelines[i] = sw_sync_timeline_create(); in test_merge_stress_random_merge() 51 fence = sw_sync_fence_create(timelines[0], "fence", 0); in test_merge_stress_random_merge() 65 timeline = timelines[timeline_offset]; in test_merge_stress_random_merge() 101 sw_sync_timeline_inc(timelines[i], fence_map[i]); in test_merge_stress_random_merge() 112 sw_sync_timeline_destroy(timelines[i]); in test_merge_stress_random_merge()
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_engine_pm.c | 113 struct intel_gt_timelines *timelines = &engine->gt->timelines; in __queue_and_release_pm() local 136 spin_lock(&timelines->lock); in __queue_and_release_pm() 140 list_add_tail(&tl->link, &timelines->active_list); in __queue_and_release_pm() 148 spin_unlock(&timelines->lock); in __queue_and_release_pm()
|
| H A D | selftest_timeline.c | 528 struct intel_timeline **timelines; in live_hwsp_engine() local 539 timelines = kvmalloc_array(NUM_TIMELINES * I915_NUM_ENGINES, in live_hwsp_engine() 540 sizeof(*timelines), in live_hwsp_engine() 542 if (!timelines) in live_hwsp_engine() 569 timelines[count++] = tl; in live_hwsp_engine() 582 struct intel_timeline *tl = timelines[n]; in live_hwsp_engine() 593 kvfree(timelines); in live_hwsp_engine() 602 struct intel_timeline **timelines; in live_hwsp_alternate() local 614 timelines = kvmalloc_array(NUM_TIMELINES * I915_NUM_ENGINES, in live_hwsp_alternate() 615 sizeof(*timelines), in live_hwsp_alternate() [all …]
|
| H A D | intel_gt_types.h | 131 } timelines; member
|
| /linux/drivers/gpu/drm/i915/selftests/ |
| H A D | i915_mock_selftests.h | 26 selftest(timelines, intel_timeline_mock_selftests)
|
| /linux/tools/power/pm-graph/ |
| H A D | README | 53 timelines and a callgraph to give a quick and detailed view of which devices 210 to generate the data you want. It's most useful to collect dev mode timelines 247 speed up the testing by not creating timelines or summary html files. You 249 create the timelines. 255 generate the timelines and summary. 268 Used with -summary to regenerate any missing html timelines from their 293 or if you need to generate the html timelines you can use -genhtml
|
| /linux/Documentation/trace/ |
| H A D | timerlat-tracer.rst | 116 in the timelines means circa 1 us, and the time moves ==>::
|
| /linux/Documentation/process/ |
| H A D | maintainer-netdev.rst | 189 Review timelines
|